Bug #19233 Characters with Cedilla are stripped of Cedilla
Submitted: 20 Apr 2006 21:50 Modified: 26 Aug 2007 17:07
Reporter: Matt Walton Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.12.00 OS:Windows (Windows 2000 SP4)
Assigned to: CPU Architecture:Any

[20 Apr 2006 21:50] Matt Walton
Description:
When inserting characters with Cedilla into MySQL the data is stored incorrectly.  For example, the character Ņ (U+0145), is saved as N or the character Ŗ (U+0156)is stored as R.  I'm copying the characters from Microsoft's Character Map tool and inserting directly into a column of data type varchar.  Please see the example below.

How to repeat:
Tool used: Microsoft's Unicode ODBC Test tool (odbct32w.exe)
Default character set from my.ini: utf8
ODBC driver version: 3.51.12.00

1) Make a connection to the MySQL server 5.0.18

2) CREATE TABLE test (COL1 VARCHAR(25) CHARACTER SET utf8)

Not sure I need the CHARACTER SET utf8 but I added anyway.  Fails with or without.

3) INSERT INTO test values ('Ņ')

4) SELECT * FROM test

5) The result set will be N and not Ņ 

Suggested fix:
Support for characters with Cedilla
[21 Apr 2006 1:10] MySQL Verification Team
Thank you for the bug report. This isn't a server bug, instead MyODBC bug.

mysql> CREATE TABLE test (COL1 VARCHAR(25) CHARACTER SET utf8);
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO test values ('Ņ');
Query OK, 1 row affected (0.01 sec)

mysql> SELECT * FROM test
    ->
    -> ;
+------+
| COL1 |
+------+
| Ņ   |
+------+
1 row in set (0.01 sec)
[26 Apr 2006 13:44] Matt Walton
any idea if this will get addressed in a future relese of MyODBC?
thanks
[7 Nov 2006 0:25] Jess Balint
fix version to be connector/odbc version
[23 Aug 2007 13:29] Susanne Ebrecht
Hi Matt,

please, can you test this again with the newest ODBC version (3.51.19) and inform us, if the error is still occur.

Regards,

Susanne
[26 Aug 2007 17:07] Kent Boortz
The tool "odbct32w.exe" is testing Unicode, something
that is not supported in the MySQL Connector/ODBC 3.51
driver. Work is done on a new updated driver, 5.x, but
I can't say when it will be completed.