Bug #11435 User info cannot be updated when db set to utf8 as default
Submitted: 19 Jun 2005 14:08 Modified: 22 Jun 2005 12:27
Reporter: Michael Strong Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.21 OS:Windows (Windows XP)
Assigned to: Vladimir Kolesnikov CPU Architecture:Any

[19 Jun 2005 14:08] Michael Strong
Description:
When I try to update a user's information, even just their icon, I receive the following error:

** Message: [Invalid UTF-8] Error executing query  ≡↕:

How to repeat:
I created a new installation of MySql from the latest "production" version as of 6/18/2005, file name: mysql-4.1.12a-win32.zip.

I elected utf8 as the default encoding.

I installed a fresh copy of Administrator as of 6/18/2005, file name: mysql-administrator-1.0.21-win.msi.

Things worked nicely, until I tried to manage users.  I could create a new user, which is the most important thing, of course, but could not update their ancillary information (e.g., full name, street address, icon, etc.).

The error seems to indicate that the user tables and the plumbing for updating them from this utility are not prepared to deal with utf8-oriented system tables.

That may be completely wrong, but I don't have much information except that error message above.

Just FYI.
[22 Jun 2005 12:27] Vladimir Kolesnikov
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
    http://www.mysql.com/doc/en/Installing_source_tree.html
[14 Aug 2005 10:43] Paul van Rossem
Looks like regression of at least some of the bugs 12306, 9427, 9055, 7738, 9847, 5114, 9803, 4080, 9811, 3597, 9648, 9940, 7449, 3509, 9885, 11179. 

I suspect that the real problem still has not be determined since this bugs keeps popping up again and again after "being solved".