Bug #62121 Just working in the EER diagram builder...
Submitted: 9 Aug 2011 2:10 Modified: 9 Sep 2011 3:20
Reporter: Michael Brewster Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.34 CE - Rev7780 OS:Other (Win7 Ultimate)
Assigned to: CPU Architecture:Any
Tags: crash, Duplicate DB names, foreign keys, modeling, reverse engineer

[9 Aug 2011 2:10] Michael Brewster
Description:
I was manipulating an EER diagram, and adding foreign keys. I accidentally added a foreign key from a table pointing to itself. after that, everything went to ....

How to repeat:
1) Create new EER diagram.
2) Add a few tables with different relationships etc.
3) Realize you have an existing DB that would be the perfect boiler-plate/base
4) reverse-engineer that DB
5) copy the tables that result from the reverse engineer to the EER diagram you created earlier.
6) struggle to figure out how to put the tables (that you just copied) into the same DB as the one you've been working in.
7) decide renaming the DB to match the DB for the copied tables to the name of the default EER diagram is the most logical way to put them all under one roof.
8) realize that won't work....
9) start rebuilding the tables you copied under the proper DB... by hand... renaming the DB you just renamed somewhere along the way.
10) forget to save after rebuilding all the tables by hand.
11) start setting up foreign keys and wait for your demise... *crash*
12) submit a bug report.
13) be laughed at by product developers..

14) :(

Suggested fix:
Make it so I can drag and drop tables between DBs in the "Catalog Tree" pane... I was totally shocked that I could ctrl-click to pick and choose specific tables that I wanted to move over to my new DB.... but all I could do is "Refresh" em... Why would I ever select a specific set of tables while holding down ctrl and only want to refresh them? How could you possibly not be able to drag and drop them? makes no sense >.< *pulling out hair*

I freaking love MySQL Workbench... but jeezisss! this was very frustrating..
[9 Aug 2011 3:20] Valeriy Kravchuk
Thank you for the problem report. When you'll get this crash again, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this report.
[9 Sep 2011 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".