Bug #35830 deleting a fk connection in EER model causes exception

Submitted:	4 Apr 2008 13:42	Modified:	8 Apr 2008 14:27
Reporter:	Nick Warrington	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.15	OS:	Windows (XP SP2)
Assigned to:		CPU Architecture:	Any
Tags:	EER, exception, foreign key

Description:
I deleted the foreign key relationship in the table editor between two existing tables in my schema. The corresponding EER diagram did not automatically refresh. I right clicked the foreign key relationship on the diagram to bring up the context menu and selected delete. This caused an exception to be thrown. (I assume because the actual relationship no longer existed in the model, but that's speculation on my part)

How to repeat:
Create two tables, create a fk between them, show the tables on you EER diagram to confirm you have the relationship shown on the diagram. Delete the relationship from the table editor and then delete the same relationship from the EER diagram.

Suggested fix:
Refresh the EER diagram after modifying a table, if the entity modified is shown in the diagram.

this issue has already been fixed in our repository. (tested SVN Rev 2954)

A note has been added to the 5.0.17 changelog: 

When modifying an existing foreign key relationship, the generated ALTER script did not reflect the modification.

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.