Bug #56261 Changing Constraint Name in Diagramming results in Program Crash
Submitted: 25 Aug 2010 16:42 Modified: 30 Aug 2010 14:00
Reporter: Dev Dewboy Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.26 CE OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any

[25 Aug 2010 16:42] Dev Dewboy
Description:
I have an Diagram and I build tables. It only has about 6 tables in it with 1:n relationships; I have created the columns myself and then assign the relationship from table to table. Data is saved. 

The names the FK constraints built normally have a 1 at the end (which I don't like by the way), so I go to the table's Foreign Keys Tab and remove the 1. 

I then go to the next table and double-click it to bring up the edit tabs and BAM! Microsoft Visual C++ Runtime Library pop-up error R6025 - pure virtual function call. This occurs after about every other Foreign Key name changed.

How to repeat:
See above. edit different table's FK names. You should be able to get it no problem.
[25 Aug 2010 18:51] Valeriy Kravchuk
Please, upload .mwb file and exact steps to perform on it to demonstrate the problem.
[25 Aug 2010 18:58] Dev Dewboy
sample MWB to reproduce error

Attachment: testbug.mwb (application/octet-stream, text), 6.55 KiB.

[25 Aug 2010 19:01] Dev Dewboy
I have uploaded a sample MWB. I created this one from scratch very easily and you should be able to duplicate the error quickly. It has three tables and 2 relationships. Simply go into the Foreign Keys and change the name, by deleting the last character at the end or adding a single character at the end. Then click out or save. You should get the error one the first or 2nd try.
[25 Aug 2010 19:02] Dev Dewboy
picture of error.

Attachment: error_pic.png (image/png, text), 8.58 KiB.

[25 Aug 2010 19:04] Dev Dewboy
One reproducing the error, I have described this earlier, however you may need to change to a different table (double-clicking on a table in the Modeler) after you edit a constraint on a table.
[26 Aug 2010 7:23] Ferenc Stelcz
Same bug here.

Windows XP SP3 with MySQL Workbench 5.2.26 CE Revision 6432

How to reproduce: 
- Double click a table and switch to the Foreign Keys tab
- Enter a name in the Foreign Key Name column and press enter
- Right click the recently added Foreign Key and click on Delete selected FKs
- On your diagram double click on an other table and...
Workbench crashes.

Reproducible: always
[29 Aug 2010 12:53] Valeriy Kravchuk
Verified as described in the last comment.
[29 Aug 2010 12:55] Valeriy Kravchuk
Repeatable also with .mwb uploaded as described initially on XP SP3.
[30 Aug 2010 14:00] Alfredo Kojima
This is a duplicate of bug #56219