MySQL Bugs: #67970: Synchronization of foreign keys from db to model crashes workbench

Bug #67970	Synchronization of foreign keys from db to model crashes workbench
Submitted:	24 Dec 2012 8:40	Modified:	14 Jan 2013 21:13
Reporter:	Ingo Korndoerfer	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	44	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I have now been able to narrow down problems I have reported previously, which could back then not be really nailed down to what the problem was.

Synchronization of foreign keys from a model to the workbench reproducibly crashes the workbench. While I previously thought this was an issue of foreign keys generated externally, I have now noticed this is even the case if these foreign keys were generated by the workbench itself.

How to repeat:
- Open your model, make sure it is completely synchronized.
- Generate new relationships/foreign keys in a diagram. Correct the such generated foreign keys for the bug described elsewhere already: make the foreign keys point to the proper columns (rather than newly autogenerated indexes, although you HAVE clicked on the proper columns when generating the relationships) and delete the autogenerated indexes.
- Synchronize the model (i.e. generate the keys in the db)
- Quit the workbench without saving.
- Re-open your model
- Synchronize to import the newly generated foreign keys from your db into the model (are not there yet, since we closed without saving)
==> workbench crashes

Please try version 5.2.45. Thanks.

Have worked now for two days with version 45 and have not had a single crash. That is excellent.

Not a problem anymore.