MySQL Bugs: #7768: Umlaut

Bug #7768	Umlaut
Submitted:	10 Jan 2005 13:14	Modified:	31 Mar 2014 8:14
Reporter:	Philipp Hofmann	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / J	Severity:	S1 (Critical)
Version:	3.1.6	OS:	Windows (Windows XP SP2)
Assigned to:	Alexander Soklakov	CPU Architecture:	Any

Description:
We use a MySQL 4.0 database on a linux server and MySQL Connector/J 3.0.16. There is no problem with the umlaut, e.g. Düsseldorf (Duesseldorf, D&uml;sseldorf). If we update to version 3.1.6 the umlaut will be read incorrect.

How to repeat:
Fill in the word Düsseldorf in the database. Read it with the MySQL Connector/J 3.1.6. You will get D#sseldorf instead of Düsseldorf.

testcase

Attachment: bug7768.java (application/octet-stream, text), 1.27 KiB.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

I tested on Windows XP SP2, java 1.5 update 1, connector-j 3.0.16 and 3.1.6, and didn't get this error. 

I attached test case I used (section Files) and results were:

MySQL-AB JDBC Driver
mysql-connector-java-3.0.16-ga ( $Date: 2004/09/30 07:35:03 $, $Revision: 1.27.2.44 $ )
Düsseldorf

and

MySQL-AB JDBC Driver
mysql-connector-java-3.1.6 ( $Date: 2004/12/09 15:57:25 $, $Revision: 1.27.4.52 $ )
Düsseldorf

Philipp, could you please check this testcase on your computer. You need for this to create table bug7768 in the 'test' database  with one char column and put there 'Düsseldorf' value.

You are right. If I use a MySQL 4.1 database on Windows Server there is no problem with the umlaut. But if I use a MySQL 4.0 database on Linux Server I won't get the word correct out of the database. The umlaut is corrupted.

Could you please to put here output of

show variables like 'char%';

from your server?

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".

I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.