Bug #3726 | German umlauts scrambled after backup | ||
---|---|---|---|
Submitted: | 12 May 2004 14:16 | Modified: | 17 Jun 2004 21:37 |
Reporter: | Franz Giner | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.02.b ALPHA | OS: | Windows (Windows XP Pro GER) |
Assigned to: | Bugs System | CPU Architecture: | Any |
[12 May 2004 14:16]
Franz Giner
[3 Jun 2004 12:38]
Ulrich Bayer
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Additional info: Hi, Thanks for your bug-report. This is fixed in the windows administrator version 1.0.4beta. I have tested it specifically with german umlauts in table/column-names and in data.
[17 Jun 2004 15:28]
Franz Giner
Just downloaded version 1.05b, still does not work: see output: CREATE TABLE `haupt` ( `nummer` bigint(11) NOT NULL auto_increment, `beschreibung` varchar(50) default '', `wert` varchar(30) default '', `stückzahl` int(11) default '0', // should be stückzahl `stückzahlalarm` int(11) default '0', // should be stückzahlalarm `stückpreis` decimal(10,2) default '0.00', // should be stückpreis `letztentnahme` varchar(50) default '', ..... or: ('AYD','M','Aydogar','Özer','1985-05-15'.... // should be 'Özer'
[17 Jun 2004 21:37]
Ulrich Bayer
As long as restoring works this is okay. (Restoring works only with the Mysql Administrator or a 4.1 mysql client) The file is encoded in UTF-8. Thus the character ü is encoded as the byte sequence of 0xC3 0xBC. In a normal text-editor this will look like you the text you have supplied.