Sorry but I'm in Oracle db since 10 years now and I use MySQL too but not for the same goal. I think that many developers need heavy database with many options (procedure, triggers, replication, objects and so on) and lightweight database too. Each have his own range of applications and utilities. So i'm not really against procedure and triggers in MySQL as long as it stay a low requierement hardware database. If it change that way to be, I'll drop MySQL and stay in Oracle for all usages. To all speaking about being stuck in one db vendor , I'll reply than in company front-end langages change far more than database. Databases are expensive so the choice is generally done for long and migration of data are expensive too so company say generally stuck in Oracle, DB2 or SQLServer for a very very long live... But the front end is another story. For various reason, often many front end are used. Only here in my firefight departement, we use: access, excel, openoffice, php, oracle forms and oracle reports. It lead the dba and the developer (oops it's the same person: me) to use views and procedure to offer a kind of abstraction level to all that tools. It's the better way to be sure that a same question will give a same result whatever is the front end. The couple MySQL/PHP is great because light and easy. I want it stay like that. So if you thing procedure is requiered go for it but keep it light in requierement and esay to use.
Slashdot Mirror
Sorry but I'm in Oracle db since 10 years now and I use MySQL too but not for the same goal. I think that many developers need heavy database with many options (procedure, triggers, replication, objects and so on) and lightweight database too. Each have his own range of applications and utilities.
So i'm not really against procedure and triggers in MySQL as long as it stay a low requierement hardware database. If it change that way to be, I'll drop MySQL and stay in Oracle for all usages.
To all speaking about being stuck in one db vendor , I'll reply than in company front-end langages change far more than database. Databases are expensive so the choice is generally done for long and migration of data are expensive too so company say generally stuck in Oracle, DB2 or SQLServer for a very very long live...
But the front end is another story. For various reason, often many front end are used. Only here in my firefight departement, we use: access, excel, openoffice, php, oracle forms and oracle reports. It lead the dba and the developer (oops it's the same person: me) to use views and procedure to offer a kind of abstraction level to all that tools. It's the better way to be sure that a same question will give a same result whatever is the front end.
The couple MySQL/PHP is great because light and easy. I want it stay like that.
So if you thing procedure is requiered go for it but keep it light in requierement and esay to use.