Bug #55152 Schema collation not saved.
Submitted: 10 Jul 2010 12:14 Modified: 2 Sep 2010 15:09
Reporter: Andrei Frolov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.25 OS:Windows
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: schema collation

[10 Jul 2010 12:14] Andrei Frolov 
Description:
Schema collation not saved.

How to repeat:
1. On Home page execute 'Create new EER Model' command.
2. On 'MySQL Model' tab execute 'Add diagram' command
3. On 'EER Diagram' tab right click on 'mydb' in the 'Catalog Tree', execute 'Edit Schema...' command from context menu. 'mydb' properties tab is shown with Collation value = 'lati1 - latin1_swedish_ci'.
4. Change collation value to 'Server default', close 'mydb' tab.
5. On 'EER Diagram' tab right click on 'mydb' in the 'Catalog Tree', execute 'Edit Schema...' command from context menu. 'mydb' properties tab is shown with Collation value = 'Server default'
6. Change collation value to any other value from the list (i.e. 'utf8 - utf8_general_ci'), close 'mydb' tab.
7. On 'EER Diagram' tab right click on 'mydb' in the 'Catalog Tree', execute 'Edit Schema...' command from context menu. 'mydb' properties tab is shown with Collation value = 'Server default'.

Please note that schema collation of a reverse engineered database is set to 'Server default'.
[11 Jul 2010 12:29] Valeriy Kravchuk 
Thank you for the bug report. Verified just as described on Windows XP SP3.
[23 Jul 2010 17:38] Valeriy Kravchuk 
Bug #55514 was marked as a duplicate of this one.
[5 Aug 2010 16:21] Valeriy Kravchuk 
Bug #55783 was marked as a duplicate of this one.
[26 Aug 2010 8:56] Johannes Taxacher 
fix confirmed in repository
[2 Sep 2010 15:09] Tony Bedford 
An entry has been added to the 5.2.27 changelog:

The schema collation was not saved after being changed in the Table Editor.