Bug #54865 | Entering ENUM() data type in modeler reverts to previous data type when complete | ||
---|---|---|---|
Submitted: | 28 Jun 2010 17:17 | Modified: | 30 Jun 2011 10:08 |
Reporter: | Jason Gillman Jr. | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S1 (Critical) |
Version: | 5.2.24 | OS: | Windows |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | Data Type, Modeler, MySQL Workbench |
[28 Jun 2010 17:17]
Jason Gillman Jr.
[28 Jun 2010 17:20]
Jason Gillman Jr.
Looks like this is similar to Bug #45607, however, even just entering ENUM gives the same result of reverting back to previous data type.
[28 Jun 2010 17:34]
MySQL Verification Team
Thank you for the bug report.
[29 Jun 2010 7:03]
Mike Lischke
Jason, can you confirm that this also happens with a valid ENUM definition. The data type is usually reverted if it is not valid as such (e.g. ENUM('a',b) will not be accepted). However, as soon as the type is correct it stays.
[29 Jun 2010 15:49]
Jason Gillman Jr.
Mike, You are correct, ENUM('Data','More Data') does work. Maybe this might not be so much a bug as initially thought. Perhaps change the behavior so that when ENUM("Data","More Data") is used, it converts the double-quotes to single-quotes?
[29 Jun 2010 17:16]
Valeriy Kravchuk
Converting ENUM("a","b") to ENUM('a','b') would be a nice feature to have.
[17 Feb 2011 12:35]
Mike Lischke
I added a message which tells the user when the data type is invalid. Automatic conversion of double to single quotes might lead to unwanted changes and hence will not be implemented (keep in mind with ANSI quotes enabled double quotes are used to allow to escape ids).
[30 Jun 2011 10:08]
Jon Stephens
Fixed in 5.2.32.