Bug #13113 some simplfied chinese could not store properly under utf8
Submitted: 11 Sep 2005 16:43 Modified: 30 May 2013 7:25
Reporter: terry leung Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:3.5.11-2 OS:Microsoft Windows (win2000)
Assigned to: CPU Architecture:Any

[11 Sep 2005 16:43] terry leung
Description:
Some common use characters could not store porperly, when I use MS Access 2002 as front-end.

How to repeat:
[13 Sep 2005 9:50] Aleksey Kishkin
Terry, we need a testcase for handling this bug.
[15 Sep 2005 4:03] terry leung
The table creation script as follows:

CREATE TABLE `voucher` (
  `TDate` date default NULL,
  `TVoucher` varchar(10) character set latin1 default NULL,
  `TEntity` int(10) unsigned default NULL,
  `TPayment` varchar(10) character set utf8 default NULL,
  `TIsIn` tinyint(3) default -1,
  `TLock` tinyint(3) default 0,
  `CreateAt` timestamp NOT NULL default CURRENT_TIMESTAMP,
  PRIMARY KEY  (`TVoucher`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

I connected MySQL 4.1.14 through MyODBC 3.5.11-2 in Windows 2000 Simplified edition SP4 installed. Unfortunately, 'TPayment' field couldn't properly store 'cash' in chinese either I pump data through action query or form in MS Access 2002.
[16 Sep 2005 7:20] Vasily Kishkin
Could you please attach utf-8 file with chinese values. Sorry I can't enter chinese characters on my computer. I hope I will be able to copy and paste the values.
[17 Sep 2005 2:26] terry leung
I send dataset in Excel, so you can test it. I notice that MS Office use ucs2 to handle unicode string from its offical web site. However, the problem still there when I test with MySQL 4.1.6 which support ucs2.

For my usage, I always swap between simplified and tranditional chinese OS. That's why I choose utf8 instead of native big5 and gb2312.
[24 Sep 2005 10:18] Vasily Kishkin
Thanks for Excel file.  Could you please try to insert the values from MySQL Query ? I guess you will have same result.
[25 Sep 2005 16:31] terry leung
I try this with sucess in my simplified chinese machine
1. uninstall MySQL 4.14
2. uninstall MyODBC 3.5.11-2
3. install MySQL 5.12beta
4. re-install MyODBC 3.5.11-2

I should re-intall the ODBC driver since nothing change if I don't.
However, I do the same things in my traditional chinese machine. The ODBC driver crash Access 2002. The problem remain unchange after I re-installed the driver several times
[4 Oct 2005 7:38] Vasily Kishkin
Sorry...I would like you try to insert data non-using ODBC dirver. Could you please try to insert the values using MySQL Query (you can download MySQL Query from http://dev.mysql.com/downloads/query-browser/1.1.html ). Thanks.
[5 Nov 2005 0: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".
[30 May 2013 7:25] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.