MySQL Bugs: #4032: Turkish Encoding Problem .NET Drivers

Bug #4032	Turkish Encoding Problem .NET Drivers
Submitted:	7 Jun 2004 7:42	Modified:	21 Oct 2004 21:35
Reporter:	sadun sevingen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	nt-4.0.12	OS:	Windows (windows XP & Server 2003)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
any selected turkish data cannot be displayed in correct symbols.
(some chars: þ ð ü ç ö Ý Þ Ð Ü Ç Ö )

any other application don't cause this problem.

Server Lang: latin-1
Turkish CharSet: iso-8859-9 & windows-1254 

How to repeat:
on every turkish systems.

Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

In MySQL 4.0, you have to set the server to the character set you wish to use.  The reason is that the .NET driver attempts to convert all strings that come from the database to the character set specified by the server.  We do this because we want users to be able to store and display different languages on any version of Windows.  For example, I should be able to view Japanese characters in an app running on an English system.

In MySQL 4.1, we have much strong character set support and you can specifiy character sets for a database, table, and field.  Using UTF8 for the field, Turkish characters work fine.  Using latin5 for the field, there appears to currently be some issue.  I have a unit test in my test suite now for latin5 and will keep working on it.