MySQL Bugs: #46695: Incorrect db collation in forward enginering dialog

Bug #46695	Incorrect db collation in forward enginering dialog
Submitted:	13 Aug 2009 13:22	Modified:	18 Aug 2009 16:57
Reporter:	Anton Danilchenko	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.16	OS:	Linux (Ubuntu x64)
Assigned to:		CPU Architecture:	Any
Tags:	collation, encoding

Description:
Incorrect collaption in database reverce enginering dialog.

How to repeat:
1. create empty project in workbench and set default collation in utf8
2. reverce enginering a 2 tables from existing database. This tables in Latin1 encoding
3. in workbench double click on each table and change it collation to utf8_general_ci
4. select "Database - Forvard engineer..."
5. click next and next
6. show SQL queries with fragment like this:

CREATE SCHEMA IF NOT EXISTS `st` DEFAULT CHARACTER SET latin1 ;
USE `st`;

7. "latin1" - incorrect value. I set utf8 for database in workbench project. Please, set correct collaption.

This behavior isn't repeatable with Windows Version.

I am not able to repeat this on Linux too.

Honestly I missunderstood you here a little bit.

During Analyzing I found bug #46715

After reading your bug report three times I figured out you wanted to tell us exactly what I found.

Just because before our development will misread here too I will set this bug here as duplicate of bug #46715.

And of course I will make a comment in the other bug report that for more informations they should read here.

Please sorry, but this not a bug. I test on latest x.x.17 version and all right!