Bug #50977 Crashed when tried to create a foreign key connection
Submitted: 8 Feb 2010 6:28 Modified: 9 Mar 2010 10:25
Reporter: Howard Johnson Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.15b OS:Microsoft Windows (Windows 7 x64 (but running x32 workbench))
Assigned to: CPU Architecture:Any
Tags: exhisting, field, foreign, key, recreating

[8 Feb 2010 6:28] Howard Johnson
Layed out a bunch of reverse engineered tables.  Organized and connected them.  Then deleted a one to may relationship created using a new key (added to the bottom of the table) in the one table.  But then tried to create a one to many to replace the connection I had deleted, but instead using my existing field in the one table and it crashed.

Thanks for the great tool.  I've been looking for something to replace Access for some time and you guys are seeming to work that way, and better.

Exception = System.AccessViolationException
Message = Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
FullText = System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at wb.ModelDiagramForm.handle_mouse_button(ModelDiagramForm* , MouseButton , Boolean , Int32 , Int32 , EventState )
   at MySQL.Workbench.ModelViewForm.OnMouseUp(MouseEventArgs e, Int32 X, Int32 Y, Keys keystate, MouseButtons buttons)
   at MySQL.GUI.Workbench.ModelDiagramForm.CanvasPanel_MouseUp(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
   at MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
.. hope we don't get to this later.

Suggested fix:
further testing is needed.  Not ready for prime time yet.  Suggest you go through each bit of code more carefully.  I know it takes a lot of time.  But it's the only way to make your code robust.
[9 Feb 2010 10:25] Susanne Ebrecht
Many thanks for writing a bug report.

For making deeper analysis of this we need to know how we could reproduce this.
[10 Mar 2010 0: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".