Bug #60478 Case changes in ENUM values are not recognized
Submitted: 15 Mar 2011 15:31 Modified: 17 Nov 2011 19:03
Reporter: Matthias Maier Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.33 CE OS:Any (Windows XP SP 3, Mac OS X)
Assigned to: CPU Architecture:Any
Tags: case sensitive, changes, collation, enum

[15 Mar 2011 15:31] Matthias Maier
Description:
Changes in ENUM values are not recognized in MySQL Workbench if only the case of a value was changed trying to alter a table. I would expect that any change to an ENUM value would result in an alter table command.

(MySQL 5.1.34)

How to repeat:
1) Create database:
CREATE DATABASE `test` /*!40100 DEFAULT CHARACTER SET latin1 */;

2) Right click on schema (`test`)

3) Select 'Create Table ...'
CREATE  TABLE `test`.`test_tbl` (`test_enum` ENUM('sensitive') NULL )
ENGINE = MyISAM
DEFAULT CHARACTER SET = latin1
COLLATE = latin1_general_cs;

4) Right click on table (`test`.`test_tbl`)
	
5) Select 'Alter table ...'
	
6) Change enum to: ENUM('Sensitive')
	
7) Apply changes
	
"No changes to object were detected."

Suggested fix:
Every change to an ENUM should be detected and result in an alter table command if 'apply' button is pressed.
[15 Mar 2011 15:34] Matthias Maier
Manual says: "Note that ENUM columns can be assigned a character set and collation. For binary or case-sensitive collations, lettercase is taken into account when assigning values to the column." (http://dev.mysql.com/doc/refman/5.1/en/enum.html)

Perhaps duplicate of bug #6206 or bug #7617?
[15 Mar 2011 16:50] Valeriy Kravchuk
Thank you for the bug report. Verified on Mac OS X while working with local MySQL server 5.1.57.
[17 Nov 2011 19:03] Philip Olson
Fixed as of 5.2.37:
+        Case changes to <literal>ENUM</literal> values were not
+        recognized by &workbench;.