MySQL Bugs: #56606: Changing table after chaning FK column causes error

Bug #56606	Changing table after chaning FK column causes error
Submitted:	7 Sep 2010 9:50	Modified:	7 Sep 2010 10:11
Reporter:	Kai Sautter (Basic Quality Contributor)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S1 (Critical)
Version:	5.2.26	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
If after a foreign key relationship and the corresponding column(s) in one table and you change to a different table (unrelated to the foreign key relationship) workbench's modelling view generates a fatal C error.

Any changes not saved previously will be lost.

How to repeat:
(1) Create three tables (with key and possible foreign key columns, but without defining the foreign keys)
(2) Switch to the Diagram view
(3) Build a foreign key relationship for two of the tables
(4) This will result in an additional column created in at least one of the tables to satisfy the foreign key relationship
(5) Double-click the table that got an additional column (or select Edit Table from its context menu) and change (in this sequence):
    (a) The foreign key definition to use the foreign key column previously defined for the table (on the "Foreign Keys" tab)
    (b) Delete the automatically created column on the "Column" tab
(6) Now activate the table editing pane for a different (i.e. the third) table, which will result in the error to occur and Workbench to close.

Sorry, seems to be not reproducible, i.e. fixed, on 5.2.27. I should have checked this before. Thanks.

I can't repeat this with a newer version, 5.2.27, on Windows XP SP3. Please, check if it is repeatable for you with 5.2.27.

Please see previous comment [7 Sep 11:59]. I did the same check in parallel and noted, that is seems to be fixed in 5.2.27. Which is great. My apologies, being too quick here in indicating a (potential) bug.

Not repeatable with 5.2.27.