Charset Latin 1

[peterlaursen]

I think something went wrong with the new charset settings as of BETA3 connections manager. Or is this a MySQL issue. Or a 'Peter issue' ?

At my ISP I have a 4.0.26 MySQL server running Latin1 as default charset. If I specify ASCII or DEFAULt it works with my nationals æøåÆØÅ. If I choose LATIN1 then some other glyphs appear! This is the same for HTTP-connection and direct connection.

Also the same on MySQL 5.0.19 on my local

I think I can recognize a czech 'r-with a-hacek 'and that character/glyph belongs to LATIN2 (that is not available) I believe. When I enter a Danisk 'ø' is is immeditately transformed to a 'r-with-a-hacek' when saved.

HISTORY on 4.0.26 shows:

Quote:

Set character_set_results=latin1

HISTORY on local 5.0.19 shows:

Quote:

Set character_set_connection=utf8

Set character_set_client=utf8

Set character_set_results=latin1

Now as this server is running uft8 right now this is what one would expect.

After changing server default to latin1 HISTORY shows

Quote:

Set character_set_connection=latin1

Set character_set_client=latin1

Set character_set_results=latin1

and the display is the same. No 'ø' but a 'r-with-a-hacek'.

However choosing 'DEFAULT' from connection manager HISTORY shows:

Quote:

Set character_set_connection=latin1

Set character_set_client=latin1

Set character_set_results=default

and 'ø' is displayed

'ø' is only chosen as an example. 'æ' and 'å' also displays as some central/eastern European characters (a Polish accented l (pronounced as 'w') for instance!

If I manully issue 'Set character_set_results=latin2' those characters are displayed as '?' and in a HEX-editor they ae identified as char(63) after SQL- and CSV-export.

To the extent that I can verify other charset settings are OK (cyrillic cp1251, Arabic tis620)

So I really do not understand!

[peterlaursen]

BTW:

I think we will see more charset options in the connections manager for the future.

I request a TAB in preferences where users can check which ones should be displayed in connections manager. Most users will only need a few!

[peterlaursen]

Now it is not reproducable with MySQL command-line:

Code:

Welcome to the MySQL monitor. Commands end with; or g.
Your MySQL connection id is 43 to server version: 5.0.19-nt-max

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> use test;
Database changed
mysql> select * from t1;
Empty set (0.00 sec)

mysql> show variables like '%character%';
+————————–+——————————————————+
| Variable_name | Value |
+————————–+——————————————————+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | C:programmermysqlMySQL Server 5.0sharecharsets |
+————————–+——————————————————+
8 rows in set (0.00 sec)

mysql> insert into t1 values (1,'æøå');
Query OK, 1 row affected (0.03 sec)

mysql> select * from t1;
+—-+——+
| id | t |
+—-+——+
| 1 | æøå |
+—-+——+
1 row in set (0.00 sec)

Welcome to the MySQL monitor. Commands end with; or g.
Your MySQL connection id is 45 to server version: 5.0.19-nt-max

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> show variables like '%character%';
+————————–+——————————————————+
| Variable_name | Value |
+————————–+——————————————————+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | C:programmermysqlMySQL Server 5.0sharecharsets |
+————————–+——————————————————+
8 rows in set (0.00 sec)

mysql> Set character_set_connection=latin1;
Query OK, 0 rows affected (0.00 sec)

mysql> Set character_set_client=latin1;
Query OK, 0 rows affected (0.00 sec)

mysql> Set character_set_results=latin1;
Query OK, 0 rows affected (0.00 sec)

mysql> use test;
Database changed

mysql> select * from t1;
+—-+——+
| id | t |
+—-+——+
| 1 | æøå |
+—-+——+
1 row in set (0.00 sec)

Does this not look like an issue with the API ?

[peterlaursen]

This issue is no longer reproducable with SQLyog 5.1 BETA 4.

What fixed it ?

[Ritesh]

Couple of bug fixes regarding charsets. This area is still under development and expect some more fine tuning in coming BETAs.

[Author]

Posts