Bug #54947 Attempt to read/write protected memory when changing foreign key column
Submitted: 1 Jul 2010 23:22 Modified: 10 Aug 2010 10:37
Reporter: Ryan Shelley Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.25 CE OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[1 Jul 2010 23:22] Ryan Shelley
Description:
When attempting to change the column associated with a foreign key, a memory protection error appears.

How to repeat:
Create two tables with several columns.  Add a one to many non-identifying relationship between the tables.  Go to the Foreign Keys tab of the foreign key table and attempt to change the key column from the default column created when the relationship is added, to an existing column already in the table.  Attempted to remove the new column and select the original column from the Foreign Key tab does the same thing.

Suggested fix:
Allow you to change the column associated with the foreign key relationship?
[2 Jul 2010 4:13] Valeriy Kravchuk
I do not see this problem on Mac OS X. Should be Windows-specific.
[6 Jul 2010 10:04] Susanne Ebrecht
I also have no problems with Linux here.
[6 Jul 2010 15:44] Ryan Shelley
I simply removed my old column and renamed the newly created foreign key column to the name I wanted it.  Not ideal, but it's not critical.
[13 Jul 2010 10:36] Susanne Ebrecht
Do you mean you found a workaround?
[13 Jul 2010 15:45] Ryan Shelley
Yes.  I can replicate the error still, but it's not stopping me from creating my ERDs.
[27 Jul 2010 8:50] Valeriy Kravchuk
I can not repeat this on Windows XP also. What data type do your FK column(s) have?
[30 Jul 2010 0:23] Ryan Shelley
I'm not sure of the datatype, and my newest model doesn't appear to be affected.  I know this occurred on Windows 7 and not XP, if that makes any difference.  I just created another model that hasn't been saved or pushed to a DB and it seems to be working as expected.  I'm not sure what the issue was at the time, but it apparently seems resolved, mysteriously but miraculously! :)  Thanks for taking the time to attempt to validate.
[10 Aug 2010 10:37] Susanne Ebrecht
Many thanks for all your feedback.