Bug #69763 | Missing datatype options: BIT, ENUM() and SET() | ||
---|---|---|---|
Submitted: | 17 Jul 2013 8:24 | Modified: | 7 Feb 2014 8:01 |
Reporter: | Nanne Huiges | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 5.2.47, 5.2.40 and 6.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[17 Jul 2013 8:24]
Nanne Huiges
[17 Jul 2013 9:53]
MySQL Verification Team
Hello Nanne, Thank you for the bug report. Verified as described. Thanks, Umesh
[12 Aug 2013 20:07]
Richard Watson
Same problem with geometry data types.
[28 Jan 2014 4:55]
MySQL Verification Team
Confirmed on Win7 + MySQL Workbench 6.1.1.11562 build 1158 that it is no longer repeatable. - There isn't any problems when you type for example: ENUM('value') - Problem is noticed i.e a warning is popped up only when you don't pass any value to ENUM, which is expected.
[28 Jan 2014 5:01]
MySQL Verification Team
Also, there isn't any problems noticed with SET, and BIT. E.g - SET('ONE','TWO'), BIT(1) etc works
[6 Feb 2014 17:27]
Philip Olson
This appears to be a documentation bug, which is now fixed. The documentation now reads as: ENUM, BIT, and SET must contain at least one value when entering these data types into MySQL Workbench. Please add a note if this is now the case (or if a bug was fixed). Thank you for the bug report.
[7 Feb 2014 8:01]
Nanne Huiges
I'm not sure if we are talking about a fixed version of the workbench, or that there is a miscommunication, but note that: * I understand that normally you need to enter a value in ENUM for it to work * This means that typing "ENUM('value')" should work. And it does normally * This bug-report is about a specific file getting to a state where this does NOT work. It is NOT a case of "ENUM NEVER WORKS", it is a bug that workbench has created a model that is broken. so I doubt it has anything to do with documentation