Sprocs if necessary, but not necessarily sprocs

from the Artful MySQL Tips List

If you learned database programming on a big iron RDBMS like Oracle or SQL Server, you probably expect that in MySQL, too, you will implement most database logic in stored procedures.

Think again. MySQL sprocs offer no additional security or significant performance. They are compiled on a per-connection basis. Like all stored routines they encapsulate & modularise, but at the cost of requiring use of an awkward, crippled language with no debugger. Their implementation makes them very difficult to use in shared hosting environments, and that's passing strange since that's exactly where there are so many MySQL users.

Some database computation (eg edge list tree models) require stored routines. They can be used to automate some database administration tasks. But before we can apply the general rule we all learned regarding the advantages of sprocs to MySQL, the MySQL implementation of them will need to be beefed up considerably.

Return to the Artful MySQL Tips page