Bug #63859 | mySQL Model is empty after Re-Load Model | ||
---|---|---|---|
Submitted: | 27 Dec 2011 15:10 | Modified: | 22 Jun 2013 3:23 |
Reporter: | Adrian Grund | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 5.2.37 | OS: | MacOS |
Assigned to: | CPU Architecture: | Any | |
Tags: | empty, model, MySQL, only diagram |
[27 Dec 2011 15:10]
Adrian Grund
[27 Dec 2011 16:50]
Valeriy Kravchuk
I can not repeat this problem with 5.2.37 on Mac OS X 10.5.6. Please, send the .mwb file that demonstrates the problem in your environment.
[27 Dec 2011 17:01]
Adrian Grund
This is the mwb file causing that no mySQL database scheme is loaded in the mySQL tab. Just the diagramm is loaded.
Attachment: wls.mwb (application/octet-stream, text), 53.26 KiB.
[27 Dec 2011 17:30]
Valeriy Kravchuk
Verified with your .mwb file uploaded. Thank you.
[13 Jan 2012 0:40]
Phil Notick
I have a similar problem it was with an existing model that was generated in an earlier version. Not all of my models have shown this issue. but the one in question was both my largest (and most important). I went back via time machine and was able to retreive earlier versions and they show the same issue. It was able to still generate script files showing differences so things like stored procedures are there but not visibile on the "MySQL Model" window. Any work around would be appriciated short of reimporting from a database.
[16 Jan 2012 3:56]
Kwami Agbodji
I have the problem described here as well, with newly created models. Once I save and close the model, the next time I reload it, the model pane is empty. The data is there however; if I export the model tables (from the empty pane) and reimport into a new model, I can see all the objects, and the pane is displayed correctly. Similarely, if I create a new EER diagram, all the objects are present and ready for use. I'm using Workbench 5.2.37 on OSX Lion 10.7.2. Thanks.
[24 Jan 2012 10:08]
Anh Nguyen
I'm having this same problem too with a schema of about 25 tables. For me it seem the problem is related to the existent of a second schema in the model. I had a file that created the blank effect with 2 schemata and EER diagrams. I'm able to recover viewing the data by loading the model into a new file, deleting out the 2nd schema, thus leaving only the 1 schema in my model. Saving, closing and re-opening the mwb file now show the model pane correctly. Have also changed added a new column to a table to change the primary schema, saving and re-opening is still fine. Importing that 2nd schema into a new file, removing the first schema so that it's the only schema in the model file also seem to work fine with that other .mwb file. Have also verify the blank pane happen when opening the affected file on 5.2.36, and opening it on the Windows 5.2.37 work just fine and all schemas show up correct. Seem problem is only affecting OSX edition of Workbench.
[5 Feb 2012 1:28]
Kwami Agbodji
Thanks Ahn, your workaround worked like a charm. I created a new (blank) workbook, and imported the problem workbook into it via file > include new model. I then deleted one of the schema, saved and closed the file. Upon re-opening the file, the model pane correctly displays all objects. For now, I will manage my schemas in two different workbooks.
[20 Apr 2012 5:33]
Cameron Green
I had the same thing happen, also on Max OSX (Lion). Vexing as the EER diagram I created now seems to be trapped in the mwb file with the blank model schemata. I was able to get my model schemata back by importing it into a blank worksheet, which is one thing I guess. If someone is looking at this issue I can send mwb file.
[20 Apr 2012 6:05]
Cameron Green
Seem to have worked this out, and luckily it's not a data corruption issue. In my case my first schema had about 300 tables in it. When I created a second schema with a couple of tables in it, the physical schemata pane for the second schema becomes really long. So when you open up the MySQL Model tab all you see is white space, and the other sections at the bottom of the screen, schema privileges etc. The Physical Schemata is still there though, it's just a couple of pages of scrolling upwards of whitespace from where you would expect it to be. In my case I deleted the second schema and all was well again.
[22 Jun 2013 3:23]
Alfredo Kojima
Duplicate of bug #68596, fixed in 6.0 branch