Bug #39360 | EER diagram corrupted, not usable anymore | ||
---|---|---|---|
Submitted: | 10 Sep 2008 7:31 | Modified: | 17 Dec 2008 16:10 |
Reporter: | - - | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 5.0.24, 5.0.26, 5.0.27 | OS: | Any |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[10 Sep 2008 7:31]
- -
[10 Sep 2008 8:21]
Valeriy Kravchuk
Thank you for a problem report. Please, upload problematic .mwb file.
[10 Sep 2008 8:33]
- -
I'm sorry, I can't upload mwb file, our database schema is confidential.
[10 Sep 2008 8:43]
Valeriy Kravchuk
Then I need a repeatable sequence of actions (not related to your confidential schema) to reproduce the problem. This will speed up bug fixing a lot.
[10 Sep 2008 8:54]
- -
Well I can't say much more : I have selected a dozen of relationships to hide them, then I have selected a table, then I tried to move this table using drag&drop before having this exception. Since I had same exception each time I perform an action on this diagram (e.g. move or edit a table), I closed Workbench. But it was the same issue when I reopen it. Now I can't use this diagram anymore. I am able to create another one in same mwb file, but I'd prefer to avoid re-arranging my 60 tables, and I'm now afraid to go on with this release...
[12 Sep 2008 11:34]
Valeriy Kravchuk
Please, try to repeat with a newer version, 5.0.25, and inform about the results.
[12 Sep 2008 19:36]
- -
Same result
[15 Sep 2008 16:37]
MySQL Verification Team
This happens on your side with any project file or just with that confidential one? otherwise could you provide one without confidential data?. Thanks in advance.
[16 Sep 2008 8:17]
- -
This happens only with my main EER diagram. As I said before, other EER diagrams belonging to the same mwb file work. Even if I export SQL from corrupted diagram and import it in another diagram, it works.
[14 Oct 2008 15:26]
Valeriy Kravchuk
Please, try to repeat with a newer version, 5.0.26, and inform about the results.
[15 Oct 2008 6:48]
- -
Still the same exception with 5.0.26.
[15 Oct 2008 9:33]
- -
Couldn't you provide more details when you report this kind of exceptions (i.e. the root cause) ?
[18 Nov 2008 12:16]
Susanne Ebrecht
Many thanks for all your feedback. For making a deeper analysis here we need the file from you. You can upload it by using: http://bugs.mysql.com/bug.php?id=39360&files=1 Please set the privacy field to: Only developers will be able to see the file This will occur that only the Sun MySQL employees with developer rights for MySQL bugs will see the files. Your problem sounds like a corrupted file. But Workbench should not produce corrupted files and when a corrupted file exist Workbench should not thrown off course in such a way. But for checking what goes wrong here we need the file. You also could give it a try and try the newest version 5.0.27.
[18 Nov 2008 12:44]
- -
No change with 5.0.27. I've ended up to upload corrupted file. Please, remember it's confidential. Just move a table on 'all' model.
[23 Nov 2008 21:18]
Valeriy Kravchuk
Verified just as described with your file.
[4 Dec 2008 21:34]
Johannes Taxacher
this has been fixed. fix will be in 5.0.28
[9 Dec 2008 10:24]
Tony Bedford
An entry was added to the 5.0.28 changelog: A complex EER diagram threw an exception whenever an action was peformed on it. However, other diagrams in the same MWB file functioned correctly. The exception generated was: System.Runtime.InteropServices.SEHException: Un composant externe a levé une exception. à wb.ModelViewForm.handle_mouse_button(ModelViewForm* , MouseButton , Boolean , Int32 , Int32 , EventState ) à MySQL.Workbench.ModelViewForm.OnMouseUp(MouseEventArgs e, Int32 X, Int32 Y, Keys keystate, MouseButtons buttons) à MySQL.GUI.Workbench.ModelViewForm.CanvasPanel_MouseUp(Object sender, MouseEventArgs e) à System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e) à MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseUp(MouseEventArgs e) à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) à System.Windows.Forms.Control.WndProc(Message& m) à System.Windows.Forms.ScrollableControl.WndProc(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
[17 Dec 2008 16:10]
- -
Now this bug is resolved I've been working again on it for several hours, this product really begins to rock :-)