MySQL Bugs: #73708: Diagrams completely mangled

Bug #73708	Diagrams completely mangled
Submitted:	25 Aug 2014 9:33	Modified:	1 Dec 2014 14:26
Reporter:	Georgi Sotirov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	6.2.x	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
As it appears diagrams into models are opened completely mangled into 6.2.x - all the tables are stacked one over the other on the top left and nothing is actually positioned as it was saved previously (e.g. in 6.0.x or 6.1.x). Thus the diagrams are presented into completely incomprehensible way, which is annoying, since this contradicts to the idea of modeling.

How to repeat:
1. Create a model with a diagram in 6.1.x or 6.0.x;
2. Order the tables on the diagram sheet as you prefer;
3. Save the model;
4. Upgrade to Workbench 6.2.x;
5. Open the saved model.

Suggested fix:
Revert to 6.0.x or 6.1.x and do NOT save your models into 6.2.x, because the diagrams would remain mangled.

Thank you for the bug report. Are you able to attach a screenshot?. Thanks.

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".

A mangled diagraim in MySQL Workbench 6.2.3

Attachment: wb_6_2_diagram_mangled.png (image/png, text), 25.54 KiB.

I somehow omitted to provide feedback here (and seems like this is the easiest way for closing a bug here). However, this bug completely annoys me, because today I ruined a diagram that I've worked for months beyond any possible restoration. Please, please, please fix this bug into next release, because it's totally devastating.

Was this by chance fixed in 6.2.4, because I just installed the new version and it seems OK with it. I get the feeling that the faulty behavior is sporadic, because if you do not save the model (with the mangled schema), the next time you open it there's a chance that it's opened without the problem (i.e. with schema objects well positioned).

Thank you for the feedback.