Bug #34847 MySQL Workbench 5.0.14 crashes when editing model saved with 5.0.13
Submitted: 26 Feb 2008 16:17 Modified: 29 Feb 2008 15:56
Reporter: Dejan Krsmanovic Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.0.14a OS:Windows (Windows XP SP2)
Assigned to: CPU Architecture:Any

[26 Feb 2008 16:17] Dejan Krsmanovic
This happened on 2 different machines and I also tested it with the different models. 
When editing table detail, and clicking on primary key column (in my models it is BIGINT, with NN and AI checked) application crashes. 

How to repeat:
-Open model created with 5.0.13
-Click on some table
-Click on column tab
-Click on primary key

Application crashes.
[26 Feb 2008 20:14] MySQL Verification Team
Thank you for the bug report. Could you please provide your model project
file I wasn't able to repeat and maybe could be the same issue of bug:
http://bugs.mysql.com/bug.php?id=34848. Thanks in advance.
[27 Feb 2008 9:34] Dejan Krsmanovic
I have uploaded the file. Just open it, double click on vip_notification table and in columns tab click on the notification_id column.
I have another model that has the same problems in 5.0.14
[27 Feb 2008 13:44] MySQL Verification Team
Thank you for the feedback. I was able to repeat with your model project.
[28 Feb 2008 11:00] Johannes Taxacher
dejan, could you please check again with 5.0.14a if this still occurs with our latest fix?
[28 Feb 2008 11:57] Dejan Krsmanovic
I have downloaded and installed 5.0.14a and I still have this problem. 

Note that I could not verify if I actually installed 5.0.14a, since everywhere it stays 5.0.14 Revision 2649.
[28 Feb 2008 14:52] Dejan Krsmanovic
OK, I have just tested again with the model I sent you and it seems that it works OK now. However, I have another model which has the same problems. I will upload it here
[28 Feb 2008 15:04] MySQL Verification Team
Still happens with 5.0.14a.
[29 Feb 2008 8:51] Johannes Taxacher
fixed in 5.0.14a SVN Rev 2565
[29 Feb 2008 15:56] Peter Lavin
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
Added to the changelog for version 5.0.14a.