Bug #56856 Updating Foreign Key in EER Diagram
Submitted: 19 Sep 2010 12:52 Modified: 19 Oct 2010 18:20
Reporter: Edwin Rodriguez Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.26 CE Revision 6432, 5.2.27 OS:Windows (Unexpected Error)
Assigned to: CPU Architecture:Any
Tags: EER Diagram, foreign keys

[19 Sep 2010 12:52] Edwin Rodriguez
Description:
When I was trying to update Foreign Key int he EER Digram tab, I recieved the following errror:

------------------
MySQL Workbench has encountered a Problem

Attempted to read or write protected memory.  This is often an indication that other memory is corrupted.
------------------

How to repeat:
Selected Create EER from SQL
Selected the SQL file
Deleted a table that was no longer required
Selected the table I wanted to edit
Clicked the Foreign Key tab
Typed a value into the Foreign Key Name
Attempted to select a Reference table
Received the above error

Suggested fix:
None
[19 Sep 2010 12:53] Edwin Rodriguez
This error does cause MySQL Workbench to crash.
[19 Sep 2010 12:56] Edwin Rodriguez
Sorry, my mistake the statement that it causes MySQL Workbench to crash.  The bug needs to be reported, then I can close the Error Dialog box and continue.
[19 Sep 2010 13:10] Edwin Rodriguez
It seems that every time I tab out of the type column I am getting the error regardless of what tab I am on.  This has now happed on the indexes tab.
[19 Sep 2010 13:35] Valeriy Kravchuk
What exact version of Workbench, 5.2.x, do you use?
[19 Sep 2010 15:17] Edwin Rodriguez
The version that I am using is 5.2.26 CE Revision 6432.
[19 Sep 2010 15:31] Edwin Rodriguez
I just updated to Version 5.2.27 CE Revision 6485, and I am still recieving the error.
[19 Sep 2010 18:20] Valeriy Kravchuk
Please, upload problematic .mwb file to apply steps in "How to repeat" section to get the problem.
[19 Oct 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".