Bug #10981 | bad conversion unicode <-> cp1250 | ||
---|---|---|---|
Submitted: | 31 May 2005 10:20 | Modified: | 8 Jun 2005 13:23 |
Reporter: | ondrej lehocky | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.0.20 | OS: | Windows (windows) |
Assigned to: | Vladimir Kolesnikov | CPU Architecture: | Any |
[31 May 2005 10:20]
ondrej lehocky
[31 May 2005 13:59]
Jorge del Conde
Hi! Thanks for your bug report. Can you please upload a copy of the table that you used to test this bug ? THanks a lot
[1 Jun 2005 8:50]
ondrej lehocky
exported files from mysql databased 4.1 is on http://vk.upjs.sk/~wedec/mysql rpa 2005-31-05.sql -> is exported from phpMyAdmin 2.6.1-pl3 with CP1250 - all OK rpa_back 20050531 1232.sql -> is exported from MySQL Admin 1.0.20 with UNICODE - all BAD
[2 Jun 2005 23:43]
Jorge del Conde
Thanks for getting back to us.
[2 Jun 2005 23:46]
Jorge del Conde
To repeat, load rpa 2005-31-05.sql, export it with mysql administrator, and then use a diff. The results are self explainatory.
[7 Jun 2005 8:51]
ondrej lehocky
i try restoring DB from "rpa 2005-31-05.sql" (created with phpmyadmin, charset ok) with mysqladmin (set "file charset -> cp1250") and all is OK. when i restoring DB from "rpa_back 20050531 1232.sql", unicode charset, data is wrong, many chars is only "?"...
[8 Jun 2005 13:23]
Vladimir Kolesnikov
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: All newly created backups should be ok.