Bug #19992 latin1 used for Migration Tool session encoding
Submitted: 22 May 2006 8:05 Modified: 8 Jun 2006 16:41
Reporter: Domas Mituzas Email Updates:
Status: Closed Impact on me:
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.0.25 OS:Windows (Windows)
Assigned to: Michael G. Zinner CPU Architecture:Any

[22 May 2006 8:05] Domas Mituzas
Migration Toolkit's JDBC driver sets session character set to latin1 on target database, hence rendering all other character support useless. 

How to repeat:
Select source database that has utf8 (or any other non-latin1) data, select destination to support multilanguage, migrate the data, observe general log. 

Setting JDBC connection string (and characterEncoding) seems to fix this. 

Suggested fix:
Connection character set should be set to utf8.
[8 Jun 2006 16:41] Michael G. Zinner
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