Bug #38807 schema default collation is not correctly applied on contained tables

Submitted: 14 Aug 2008 16:44 Modified: 12 Nov 2009 10:39
Reporter: Johannes Taxacher Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.0.24 OS:Windows
Assigned to: Alexander Musienko CPU Architecture:Any
Tags: CHECKED

[14 Aug 2008 16:44] Johannes Taxacher
Description:
when collation of a  table is set to "schema default" this is not correctly applied when synching 

How to repeat:
- create a schema using utf8_czech_ci as collation for schema
- create a table (at least one PK col)
- Forward engineer this to a DB -> collation is correctly set (for tables and schema itself)
- sync the schema against the same DB again -> now WB wants to ALTER the tables collation back to 'utf8_general_ci' 

Suggested fix:
don't alter/reset collation if the user didn't change it
[11 Nov 2009 21:19] Johannes Taxacher
this has been fixed in repository and will be included in 5.2.7
[12 Nov 2009 10:39] Tony Bedford
An entry has been added to the 5.2.7 changelog:

If a collation was set as the schema default, this was not correctly handled when the model was synchronized with a live database.

If a collation was set as a schema default, and then the model forward engineered to a database, then the collation was correctly set. If however, the model was then synchronized with the live database, MySQL Workbench attempted to alter the collations to utf8_general_ci.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.