Bug #3597 Can't modify user info
Submitted: 29 Apr 2004 6:43 Modified: 1 Jul 2004 10:19
Reporter: xu jie Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S2 (Serious)
Version: OS:Windows (WinXP)
Assigned to: Alfredo Kojima CPU Architecture:Any

[29 Apr 2004 6:43] xu jie
There is something wrong when I modify the user info,error info:
Error while storing the user infomation.

MySQL Error Nr.1266
Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '='

How to repeat:
UserAdministration->User Information->modify 'Additional Information'->Apply Changes
[11 Jun 2004 6:43] Alfredo Kojima
This happens because in previous versions, the user_info table was created with
a different character set from what is expected. A quick fix for now, is to drop that table (user_info in the mysql schema/database). It should be recreated automatically.
[18 Jun 2004 18:15] Stanislas Renan
I experience a similar problem, but I noticed :
-the error message indicates latin1_bin, not swedish ;
-the default encoding of the tables are swedish ;
-dropping the table user_info does not fix the problem ;
-changing charset of all "mysql" tables to utf8 does not fix the problem ;
-defining default encoding to utf8 (and general collating) does not fix the problem ;
-defining latin1 as default encoding (and bin collating) does not fix the problem ;
-defining latin1 as default encoding (and swedish collating) does not fix the problem.

Using mysql client from the command line shows no problem : I can query
« select User from user where user='someone' »
without error.

I'm quite confused : the "latin1_bin" error message is always there, whatever the default encoding is set to, and even if the table user_info has been dropped.
[1 Jul 2004 10:19] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at