Bug #80562 | See Bug #80017 | ||
---|---|---|---|
Submitted: | 29 Feb 2016 17:37 | Modified: | 29 Feb 2016 22:59 |
Reporter: | Warren Hennemuth | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | mysql 5.7.11, workbench 6.3 | OS: | Windows (7) |
Assigned to: | CPU Architecture: | Any | |
Tags: | modeling, workbench |
[29 Feb 2016 17:37]
Warren Hennemuth
[29 Feb 2016 19:20]
MySQL Verification Team
model opened
Attachment: krim.png (image/png, text), 251.43 KiB.
[29 Feb 2016 19:22]
MySQL Verification Team
Thank you for the bug report. Please see attached picture. Thanks.
[29 Feb 2016 22:59]
Warren Hennemuth
Hi Miguel. Apparently I can remedy the situation by shutting down mysql workbench and opening it up again. This problem seems to occur when you first create the .mwb file by saving a model, closing the model view, and then trying to reopen the model view by navigating to the saved .mwb. This would make it impossible for you to recreate unless you had the entire database. It's not solved, but let's consider this closed as it's not a blocker, has a workaround, and is probably an out-layer anyway.