Bug #16774 Error messages should be converted to client encoding
Submitted: 25 Jan 2006 10:34 Modified: 28 Mar 2006 11:18
Reporter: Alexander Kirillov Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.18 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any

[25 Jan 2006 10:34] Alexander Kirillov 
Description:
The server doesn't seem to perform any character conversions when sending error messages to a client. Looks like messages always appear in the encoding used in errmsg.txt and embedded db names in UTF-8. So there's currently no workaround if you want to display non-ASCII error messages AND use non-ASCII names for db objects.

How to repeat:
Change language settings in my.cnf:
language=russian

$ mysql -p
> SET NAMES koi8r;
> DROP DATABASE `non-existent koi8r name`;
# the message is OK but db name is garbled

$ mysql -p
> SET NAMES utf8;
> DROP DATABASE `non-existent koi8r name`;
# db name is OK but the message is garbled

Suggested fix:
Should probably use UTF-8 to store server messages internally and apply
conversion rules when sending error messages to a client
[28 Mar 2006 11:18] Ramil Kalimullin 
see bug #1406