Bug #46715 wrong charset used in forward engineering
Submitted: 14 Aug 2009 11:07 Modified: 27 Oct 2009 6:30
Reporter: Susanne Ebrecht Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.1 SE OS:Linux
Assigned to: CPU Architecture:Any

[14 Aug 2009 11:07] Susanne Ebrecht 
Description:
1) Use mysql CLI:

CREATE DATABASE bla CHARACTER SET LATIN1;
USE bla;
CREATE TABLE t(v varchar(100));
CREATE TABLE t2(v varchar(100));

2) Use Workbench and reverse engineer database bla.

Change database collation to utf8_general_ci

change both table collation to utf8_general_ci

3) Forward engineer database to another MySQL instance

CREATE SCHEMA IF NOT EXISTS `bla` DEFAULT CHARACTER SET latin1 ;

Why latin1?

I said utf8!

How to repeat:
See above

Suggested fix:
Seems that charset or better collation is not checked here.
[14 Aug 2009 11:29] Susanne Ebrecht 
Bug #46695 is marked as duplicate of this bug here.

Please also read that bug for getting further informations.
[28 Sep 2009 23: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".
[27 Oct 2009 6:30] Susanne Ebrecht 
Thank you for your bug report. This issue has been committed to our source repository of MySQL Workbench 5.2 and will be incorporated into the next release.