Bug #46513 workbench collation cannot be set to model or database default (null) once set
Submitted: 2 Aug 2009 16:57 Modified: 27 Nov 2009 14:55
Reporter: Ken Brown Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.2 OS:Linux (Ubuntu 9.04)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: collation, reset, workbench

[2 Aug 2009 16:57] Ken Brown 
Description:
cannot reset collation to be model or database default once a collation has been selected on the table - i.e. set back to null

How to repeat:
create table
set collation
cannot then clear collation so it inherits model/database settings

Suggested fix:
add addional drop down as model/database default
put this at the top of the list
[2 Aug 2009 17:53] Valeriy Kravchuk 
Thank you for the problem report. Verified just as described.
[3 Sep 2009 9:53] Evert Harmeling 
I have the same...

In Workbench my MySql Schema is defined as 'utf8 - utf8_unicode_ci' and all my tables are defined with collation 'Schema Default'

My database is already set to 'utf8_unicode_ci' now, and my tables are also 'utf8_unicode_ci'

When I want to 'Synchronize Model', Workbench wants to set all my tables to ' utf8_general_ci' but it should set everything to 'utf8 - utf8_unicode_ci'...?
[6 Nov 2009 3:44] Alfredo Kojima 
Added a blank item to table and column collation combos to allow "unsetting" collation option.
[27 Nov 2009 14:32] Johannes Taxacher 
fixed in repository. will be included in 5.2.10
[27 Nov 2009 14:55] Tony Bedford 
An entry has been added to the 5.2.10 changelog:

If a collation was changed for a table in the Table Editor, there was no facility to then set this back to the schema default.

A new entry has been now been added to the collation selection listbox - Schema Default.