Bug #56496 | MySQL Workbench crashes when defining a foreign key for a table | ||
---|---|---|---|
Submitted: | 2 Sep 2010 12:45 | Modified: | 17 Sep 2010 14:57 |
Reporter: | Marco Lorefice | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 5.2.27 | OS: | Any (Windows XP SP3) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[2 Sep 2010 12:45]
Marco Lorefice
[2 Sep 2010 12:50]
Valeriy Kravchuk
Thank you for the problem report. Please, send the results of Help > System Info menu item. Are you creating self-referencing foreign key or just a foreign key from some other table? What data type(s) PK columns have?
[6 Sep 2010 21:21]
MySQL Verification Team
Thank you for the feedback. Could you please provide a model file before applied action in step 3?. Thanks in advance.
[9 Sep 2010 8:11]
Valeriy Kravchuk
Thank you for the bug report. Verified as described in last private comments.
[14 Sep 2010 6:05]
Alfredo Kojima
Fixed. Thank you for the test case.
[16 Sep 2010 19:49]
Johannes Taxacher
fix confirmed in repository
[17 Sep 2010 14:57]
Tony Bedford
An entry has been added to the 5.2.28 changelog: While attempting to define a foreign key for a table with a composite primary key, MySQL Workbench crashed. This happened while trying to select the fields of the composite primary key to be associated with the referenced columns.