| Bug #43000 | ENUM editing should be improved | ||
|---|---|---|---|
| Submitted: | 19 Feb 2009 7:32 | Modified: | 30 Nov 2009 16:33 |
| Reporter: | Michael Skulsky | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S4 (Feature request) |
| Version: | 5.0.29 OSS | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
[19 Feb 2009 7:47]
Valeriy Kravchuk
Thank you for the reasonable feature request. Same features are needed for SET columns.
[30 Mar 2009 21:42]
Alfredo Kojima
In 5.1, a new user defined type editor will be added, with some additional help for editing enum fields. With that you can define your enums as new types and use that type in the columns.
[28 Oct 2009 8:43]
Susanne Ebrecht
I can't test this with Workbench 5.2 because of bug #48364
[31 Jan 2016 19:26]
Filipus Klutiero
I have requested a better solution in ticket #80209.
Description: Currently the way ENUM columns are edited is very inconvenient. In particular: - All edits must be done inside the same datatype entry box, which is quite small; - All enum values are displayed on the canvas, and so they are making the table too wide - If you make a mistake while entering the enum definition, Workbench silently discards all your changes, leaves the datatype blank and you have to start over How to repeat: N/A (feature request) Suggested fix: - Ideally ENUM editor should look like INSERT editor. - Only the first 1-3 values of the enum should be displayed on the canvas. If there are more values, a "..." should be added. E.g. my_enum_field ENUM('val1','val2',...) - In case the datatype field cannot be interpreted correctly, a message box should be displayed, and then focus should return to the editing field, so that a correction could be made. It is not necessary to detail the error, something like "Syntax error" is enough.