Bug #55210 crash
Submitted: 13 Jul 2010 13:32 Modified: 18 Aug 2010 13:00
Reporter: Petronel Laviniu Malutan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.25 CE OS:Windows (vista home premium)
Assigned to: CPU Architecture:Any

[13 Jul 2010 13:32] Petronel Laviniu Malutan
Description:
I've created 4 tables related each other without a PK first but with foreign key for some columns.

I did filled the inserts for each table to have as example some data, than realised I am probably needing a PK in each table so clicked in the diagram and checked PK for a column in each table 

than when trying to see the inserts by clicking the inserts TAB I was not able to see the data, but a REPORT BUG window appeared.

To see again the data I needed to close and reopen WB application !

Regards

Petronel

How to repeat:
I've created 4 tables related each other without a PK first but with foreign key for some columns.

I did filled the inserts for each table to have as example some data, than realised I am probably needing a PK in each table so clicked in the diagram and checked PK for a column in each table 

than when trying to see the inserts by clicking the inserts TAB I was not able to see the data, but a REPORT BUG window appeared.

To see again the data I needed to close and reopen WB application !

Regards

Petronel
[13 Jul 2010 13:42] Petronel Laviniu Malutan
probably I should mention that after modifying the columns as PK in each table I did a syncronise, than it happened !
[15 Jul 2010 17:21] Johannes Taxacher
Hi Petronel, could you maybe add a sample file that helps us reproducing the problem?
Did you add new columns as to act as PK columns or promoted existing ones?
I'm assuming that you're on windows, according to your description, but please also add your platform information.
thanks in advance
[21 Jul 2010 4:18] Petronel Laviniu Malutan
please do a 2 table example with a FK and 1 to many based on existing, than delete the pk and than rename the FK field to id and make it primary key. Click again on the defined INSERTS button ! It is repeating to me often!
[21 Jul 2010 4:19] Petronel Laviniu Malutan
http://imagebin.ca/view/eZwOjVu2.html
[21 Jul 2010 6:37] Petronel Laviniu Malutan
I've added or promoted or both. I can't say which one is responsible for the bug but it happened more than once doing the same thing (added, promoted, deleted FK/PK)
[21 Jul 2010 7:39] Susanne Ebrecht
I am not able to repeat this.

What exactly is the error message telling?
[21 Jul 2010 12:36] Petronel Laviniu Malutan
Under Vista Home Premium

New Model
Add diagram
Place new table
Click on columns : 
rename first column to id PK NN UQ
add column name Varchar(45) NN UQ
click on inserts and add 1 pop, 2 smith, 3 jack than check the green arrow

now place second table 
add columns id pk nn uq
and table1_name NN UQ

now place new relation based on existing keys
name to table1_name

now delete table1 column id and rename the remained name column to id

go to inserts than click columns AND BINGO MYSQL Workbench has encountered a problem. Atempted to read or write protected memory.

Can you confirm you can reproduce it too ?
[22 Jul 2010 7:52] Susanne Ebrecht
I did exact what you described and all is looking fine here.

Seems it is a Vista only problem.
[25 Jul 2010 12:35] Valeriy Kravchuk
I can not get any crash on Windows XP SP3 based on last comment.
[8 Aug 2010 15:06] Valeriy Kravchuk
Please, check with a newer version, 5.2.26, and inform about the results.
[9 Aug 2010 9:00] Petronel Laviniu Malutan
I think this version is solving the issue ! Thank you
[18 Aug 2010 13:00] MySQL Verification Team
Closing according last comment.