MySQL Bugs: #11053: Error "ODBC - Failed to call" if sjis character with '5C' is in PK field

Bug #11053	Error "ODBC - Failed to call" if sjis character with '5C' is in PK field
Submitted:	2 Jun 2005 21:47	Modified:	25 Oct 2005 15:50
Reporter:	Shuichi Tamagawa	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.11	OS:	Windows (Windows XP)
Assigned to:	Peter Harvey	CPU Architecture:	Any

Description:
When retrieving data from MS Access via MyODBC, it fails with an error (MS Access error 3146) and displays only '#NAME?' if sjis character with '5C' in hex is in the primary key field.

How to repeat:
1. create table t1(c1 char(1) primary key) default character set = sjis;
2. insert into t1 values(0x835C);
3. create DSN using MyODBC 3.51.11 and add 'SET NAMES cp932' in 'Initial Statement' field.
4. create table link to table 't1'
5. open the table 't1'

If the field is not primary key, it's OK.

Correction.

3. create DSN using MyODBC 3.51.11 and add 'SET NAMES sjis' in 'Initial Statement' field.

Thanks for your bug report.

I was able to reproduce this with MS Access 2003 & MyODBC 3.51.11-2

bug screenshot

Attachment: Image1.png (image/x-png, text), 45.12 KiB.

For insert operation, another error occurs as attached.

Screenshot for of INSERT operation

Attachment: bug#11053.PNG (image/png, text), 50.97 KiB.

c/odbc v3 (MyODBC) does not support UNICODE at this time. The plan at present is to implement UNICODE support in c/odbc v5.

Please forgive me for posting a comment so late.
But why do you say about UNICODE support?
This is an SJIS problem, isn't it?

Any update with this bug?
It seems that the bug is not fixed yet in v5.