Bug #8266 cannot change character_set from utf8
Submitted: 2 Feb 2005 13:51 Modified: 14 Feb 2005 14:18
Reporter: Martin vWysiecki Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.1.5 OS:Linux (Linux, Windows)
Assigned to: CPU Architecture:Any

[2 Feb 2005 13:51] Martin vWysiecki
Description:
Hello,
after starting query browser (connection) the clinet changes the character sets to utf8. Send allways character_set_client = utf8 (SET NAMES utf8).
Exist no possibility to change to another charset.

Greetings
Martin

How to repeat:
1. Start MySQL Browser
2. Send command SHOW VARIABLES to server.
3. Look result: lines character_set_....

Or.
1. Start mysqld with option: --log="log_file"
2. Start MySql Browser
3. Look result: line SET NAMES utf8 in log_file
[14 Feb 2005 14:18] Michael G. Zinner
Hi,

MySQL Query Browser uses UTF8 internally to be able to display all characters that might be stored in the database. It is not possible to change that but it also should be no problem.

Could you state why you want to change the charset? If you have created the tables and columns with the correct charset, the server will handle the conversion to e.g. latin1 automatically.

There has been an issue with servers older than 4.1.9, so please upgrade your server if you have an older version installed.

Mike
[22 Nov 2005 11:54] Kamil Górnik
I cannot upgrade mysql server to 4.1 because it's production server (hosting) and we'd have to force clients to modify their php code used to connect to server to execute
SET NAMES latin2;
SET CHARACTER SET latin2;
SET COLLATION_CONNECTION='latin2_general_ci';
before running any query. 
Surely clients are, well, stupid enough to not understand what that's for...
Thus it'd be great feature of mysql-query-browser to allow setting encoding.
[13 Nov 2006 19:30] Sveta Smirnova
There are bug #9006 and bug #24273 showing problem with impossibility to change client charset.