Bug #72020 Problems with accents and latin1 on W7
Submitted: 12 Mar 2014 13:29 Modified: 25 Apr 2014 20:34
Reporter: Arnaud Adant Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.0.9 OS:Microsoft Windows (7)
Assigned to: CPU Architecture:Any

[12 Mar 2014 13:29] Arnaud Adant
In the SQL Editor, accents appears with utf9 but not latin1.

set names latin1;
select convert(unhex('E5') using latin1);

This should print an å but it prints a �

How to repeat:
set names latin1;
select convert(unhex('E5') using latin1);

Suggested fix:
Fix the display.
[12 Mar 2014 14:30] Peter Laursen
Is WB (on Windows at least) guaranteed to work with any other client character set than utf8 (or utf8mb4 to the extend that there is font support)?

I don't think so!
[12 Mar 2014 14:42] Peter Laursen
CLI on Windows 7 (standard client from MySQL 5.5):

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 7
Server version: 5.5.35 MySQL Community Server (GPL)

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> SET NAMES latin1;
Query OK, 0 rows affected (0.00 sec)

mysql> SELECT CONVERT(UNHEX('C3A5') USING latin1);
| CONVERT(UNHEX('C3A5') USING latin1) |
| å                                   |
1 row in set (0.00 sec)

mysql> SELECT CONVERT(UNHEX('E5') USING latin1);
| CONVERT(UNHEX('E5') USING latin1) |
| Õ                                  |
1 row in set (0.00 sec)
[12 Mar 2014 15:24] Peter Laursen
Please ignore my last post. This is an issue with the CLI in "cmd.exe' on Windows and unrelated to the discussion here.

(the unicode variant of the CLI shipped with MySQL 5.6 for Windows may work for your test cases.  But also here you may also need to omit "SET NAMES latin1;")
[25 Apr 2014 20:34] Alfredo Kojima
Workbench assumes utf8 (or utf8mb4) as the client character set, which is set by WB when it connects. Unless there's a strong business case for supporting client charset changes triggered by the user, we will not add support for that.