Bug #45165 | can't use auto_increment attribute with user defined type, crash on workaround | ||
---|---|---|---|
Submitted: | 28 May 2009 18:15 | Modified: | 9 Jun 2009 9:25 |
Reporter: | Stas Trefilov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 5.1.12 | OS: | MacOS (10.5.7) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | CHECKED |
[28 May 2009 18:15]
Stas Trefilov
[4 Jun 2009 13:02]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described. Pretty serious bug because of the crash.
[5 Jun 2009 7:15]
Mike Lischke
These were actually two bugs in one, affecting all supported platforms. Fixed in 5.1 and 5.2.
[8 Jun 2009 16:59]
Johannes Taxacher
fix confirmed. will be included in 5.1.13
[9 Jun 2009 9:25]
Tony Bedford
An entry was added to the 5.1.13 changelog: When defining a primary key with a user-defined data type, it was not possible to set the auto-increment (AI) attribute. Clicking the AI checkbox had no effect. To circumvent this problem it was possible to temporarily change the data type of the column to a built-in data type such as INT, set the AI attribute and then change the data type back to the desired user-defined data type. The model could then be saved. However, if this model was reopened and File, Export, Forward Engineer SQL CREATE Script used to generate a script, MySQL Workbench would crash.