Comments on: MySQL upgrade to 5.1.22 and stored procedures http://northernmost.org/blog/mysql-upgrade-to-5122-and-stored-procedures/ Just another manic Monday Tue, 22 Jun 2010 09:11:55 +0000 hourly 1 http://wordpress.org/?v=3.0 By: 2ge http://northernmost.org/blog/mysql-upgrade-to-5122-and-stored-procedures/comment-page-1/#comment-631 2ge Tue, 16 Dec 2008 11:49:26 +0000 http://northernmost.org/blog/?p=5#comment-631 Thanks a lot for this, I came into same problem after upgrading. RUV - your solution is just perfect, it works :) Thanks a lot for this, I came into same problem after upgrading. RUV – your solution is just perfect, it works :)

]]> By: ruv http://northernmost.org/blog/mysql-upgrade-to-5122-and-stored-procedures/comment-page-1/#comment-628 ruv Sat, 15 Nov 2008 17:40:14 +0000 http://northernmost.org/blog/?p=5#comment-628 Using the mysql.proc table is more easy way. I created a new procedure and looked at those fields: SELECT * FROM mysql.proc WHERE name="MyTestProc"; utf8 utf8_general_ci utf8_general_ci Ok, now we can update them all: UPDATE mysql.proc SET character_set_client = 'utf8' , collation_connection = 'utf8_general_ci' , db_collation = 'utf8_general_ci' WHERE db_collation IS NULL ; Using the mysql.proc table is more easy way.

I created a new procedure and looked at those fields:

SELECT * FROM mysql.proc WHERE name=”MyTestProc”;

utf8
utf8_general_ci
utf8_general_ci

Ok, now we can update them all:

UPDATE
mysql.proc
SET
character_set_client = ‘utf8′ ,
collation_connection = ‘utf8_general_ci’ ,
db_collation = ‘utf8_general_ci’
WHERE
db_collation IS NULL
;

]]>