Bug #4080 MySQL Administrator crashes in user administration
Submitted: 9 Jun 2004 16:24 Modified: 2 Jul 2004 17:05
Reporter: Christian Kirsch Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.0.4_beta OS:Linux (Linux)
Assigned to: Alfredo Kojima CPU Architecture:Any

[9 Jun 2004 16:24] Christian Kirsch
Description:
Clicking on a user in the User Administration panel pops up an error box saying

Could not retrieve user information from server. 
MySQL Error Nr. 1267
Illegal mix of collations (latin1_german1_ci,IMPLICIT) and (utf8_general_ci, COERCIBLE) for operation '='

Acknowlediging the error by clicking on OK terminates Administrator with a segmentation fault.

MySQL version is 4.1.2_alpha, it was compiled with default collation latin1_german1_ci.

How to repeat:
see above
[9 Jun 2004 20:31] Ulrich Bayer
Hi,

As a quick work-around you can manually delete the user_info table in the mysql-database. (assuming that you have no data in it.) It should be recreated automatically with the right character-set again on the next start of the mysql-administrator.  The user_info table was created wrongly in ealier versions.
[10 Jun 2004 15:41] Christian Kirsch
> As a quick work-around you can manually delete the user_info table in the
> mysql-database.

I did - to no avail. The table is recreated automagically, but the error message remains the same.
[11 Jun 2004 11:09] Daniel Schneller
Same for me.
[30 Jun 2004 18:04] Olaf Zimmerhackl
same bug in 1.0.5 Beta, but it does not crash, deleting the table does not help either

OS: WIN2000

oz
[2 Jul 2004 2:21] Simon Dean
Confirmed on Windows XP Professional SP1 running 4.1.3-beta.
Standard install.
mysql-nt --install
connect with MySql Administrator application
clicking on user reproduces this bug.
[2 Jul 2004 2:23] Simon Dean
Also confirmed that the workaround doesn't work either.
[2 Jul 2004 11:23] Simon Dean
This is not a problem on 5.0.0-alpha.
[2 Jul 2004 17:05] Alfredo Kojima
The bug has been fixed in the code repository and the next release should have this bug fixed.

Just for the record, the following links should be helpful for people having the same problem with their own clients:
http://dev.mysql.com/doc/mysql/en/Charset-connection.html

http://dev.mysql.com/doc/mysql/en/Charset-collate-tricky.html