Bug #10122 utf-8 signs destroyed
Submitted: 24 Apr 2005 10:10 Modified: 26 Jun 2005 8:13
Reporter: Marc Bauer Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Query Browser Severity:S1 (Critical)
Version:1.1.6 OS:Windows (WinXP)
Assigned to: Michael G. Zinner CPU Architecture:Any

[24 Apr 2005 10:10] Marc Bauer 
Description:
i have created a InnoDB with default charset utf8 and utf8_general_ci. if i add now in one of the rows something contain a german umlaut like ö,ä,ü,ß and so on - they are destroyed and it looks like "A*" or something like this. it looks like query browser do not detect the database charset correctly.

How to repeat:
not sure how
[24 Apr 2005 17:49] Jorge del Conde 
This happens w/spanish characters also
[26 Apr 2005 19:28] Michael G. Zinner 
Can you check if this also is true for 5.0.4 and 4.1.11? thanks.
[27 Apr 2005 6:07] Marc Bauer 
yes - i'm using 4.1.11
[15 May 2005 10:05] Michael G. Zinner 
Could you state where the "corrupted" data is displayed? Inside Query Browser or on a webpage or in your application?

In utf8 all characters that are not ASCII characters are stored with more than one byte. So, for example "Ärger" will be stored as "Ärger". If you want to display it on a webpage that has latin1 encoding you have convert the database string to latin1 on the webpage explicitly - or you set the encoding of the webpage to utf8 in the header of the page.

If you want to store only latin1 characters in your database than you should not create the database in utf8 but in latin1. In that case the server will convert the strings from Query Browser (which are always utf8) to latin1 automatically.
[15 Jun 2005 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[21 Jun 2005 7:41] Marc Bauer 
in query browser
[26 Jun 2005 8:10] Aleksey Kishkin 
screenshoot of result set with umlauts

Attachment: bug10122.JPG (image/jpeg, text), 69.74 KiB.
[26 Jun 2005 8:13] Aleksey Kishkin 
Hi! tested against mysql qb 1.1.10 but was not able to reproduce this bug (screenshoot attached). there are many bugs were fixed sinse version 1.1.6, could you check if this bug still present on your computer with version 1.1.10?
[29 Jun 2005 6:20] Marc Bauer 
on a short review it looks ok now, but not sure. last time i saw this problem after 10 hours and many changes on db. this was not easy to repro.