Bug #49277 Using ALTER TABLE wizard to change column collation fails

• Submitted: 1 Dec 2009 17:06
• Modified: 10 Feb 2010 11:07
• Reporter: Todd Farmer (OCA)
• Status: Closed
• Category: MySQL Workbench: SQL Editor
• Severity: S2 (Serious)
• Version: 5.2 r4643
• OS: Windows (XP)
• Assigned to: Alexander Musienko
• CPU Architecture: Any
• Tags: regression

[1 Dec 2009 17:06] Todd Farmer

Description:
Using the ALTER TABLE wizard to modify an existing table with a VARCHAR(45) column, I changed the column collation from "table default" to "utf8_bin" and pressed "apply".  The pop-up to review and apply the resulting DDL script does not appear.

How to repeat:
See above.

Suggested fix:
Fix to generate appropriate DDL script.

[7 Dec 2009 14:52] Mike Lischke

This needs additional verification. I cannot reproduce the mentioned problem. Setting the collation (as well as the table engine) from any value back to server default produces invalid SQL. But that is a different bug.

[7 Dec 2009 14:56] Todd Farmer

Setting the default collation at the table level works correctly in 5.2.10 - perhaps you are testing this rather than the column-level collation?  I continue to observe this problem at the column level in 5.2.10.

[1 Feb 2010 13:48] Johannes Taxacher

fixed in repository. will be included in 5.2.16

[10 Feb 2010 11:07] Tony Bedford

An entry has been added to the 5.2.16 changelog:

In the SQL Editor, if Alter Table was invoked, and the collation for a column changed, then after clicking Apply, no changes were detected.