MySQL Bugs: #10913: Bulk Transfer change charset

Bug #10913	Bulk Transfer change charset
Submitted:	27 May 2005 12:59	Modified:	9 Jun 2006 12:16
Reporter:	Abbas Adel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S1 (Critical)
Version:	1.0.6-beta	OS:	Windows (Windows XP sp2)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
I have Access database with unicode field. 
After Migration data became ????? Although i chose Multilanguage migration.
to overcome this i manually imported Create.sql and Insert.sql, which were correct Charest, using phpmyadmin

so the problem is in bulk transfer because manually transfer works

How to repeat:
Used many access databases with unicode but the same output??????

Suggested fix:
Inserting unicode data into mysql tables should be fixed

Create.sql file

Attachment: Creates.sql (text/plain), 463 bytes.

Insert.sql file

Attachment: Inserts.sql (text/plain), 404 bytes.

Access database

Attachment: db2.mdb (application/msaccess, text), 148.00 KiB.

I was able to reproduce this bug by doing the following:

Create an access database
Make sure you have Arial Unicode MS installed
Create a table with unicode symbols
export the table to MySQL using Migration Toolkit

You'll now see how the entries where exported as ???

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html