Bug #77513 | Some hungarian characters fail to save correctly | ||
---|---|---|---|
Submitted: | 26 Jun 2015 21:42 | Modified: | 28 Aug 2015 3:47 |
Reporter: | Rob Dylan | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL for Windows: MySQL for Excel | Severity: | S3 (Non-critical) |
Version: | 1.3.4 | OS: | Windows (8.1 x64) |
Assigned to: | CPU Architecture: | Any |
[26 Jun 2015 21:42]
Rob Dylan
[28 Aug 2015 3:47]
Javier Treviño
Tested on version 1.3.4, I could save the following text using double acute accent: A megoldás egyszerű Egyszerű TEST The u with double acute accent was saved successfully, verified with MySQL Workbench the data was correctly saved. The test I performed was creating a new schema with utf8_general_ci collation, then exporting some data to feed the new table with it. Then edited the new table to insert more data with double acute accent. Since I can't reproduce this, this sounds more like a configuration problem. Although the schema is using utf8, the server variables need to be set as well to UTF8, you can use MySQL Workbench to inspect the value of other system variables like character_set_client, character_set_connection, character_set_server and character_set_system. Have you tried saving data with double acute accent directly from the MySQL Server console??
[7 Apr 2017 19:51]
Rick James
The real test for whether it is saved correctly is to do SELECT HEX(col)... -- It should come back with hex C5B1. If, instead, you get C385C2B1, you are a victim of "double encoding".