Re: Stored procedure problem on upgrade to 5.0.1

[Per-Erik Martin]

Yes, this is the one major change between 5.0.0 and 5.0.1. Stored
procedures were "global" wrt the current database before, now they
"belong" to a database, just like tables. (*)

The easiest way to upgrade is to simply put your procedure definitions
in a file and reload it in the new version. (Clear the mysql.proc
table first.)

The other way is to do what Harrison suggested: Decide which database
the procedures belong to (say "test"), and do
"update mysql.proc set db = 'test'".

Note: There is one bugfix that might affect some procedures. In 5.0.0
the standard order of declarations in a procedure was not enforced,
but it is now. (You will notice if this affects you - the procedure
simply has to be corrected in this case.)

You should also have run mysql_fix_privilege_tables first
(or done the "ALTER TABLE proc" command found at the end of
share/mysql_fix_privilege_tables.sql manually). It doesn't
affect this particular problem, but it should be done anyway.


(*) Why this change? Well, 5.0.0 was a very early release. One of the
reasons for this was to capture bugs and other suggestions from users
early on. The change was made both on users' requests and for standard
compliance reasons.

pem, Senior Software Dev., MySQL AB