MySQL Bugs: #76572: Model file cannot be saved if it was auto-saved prior to being manually saved

Bug #76572	Model file cannot be saved if it was auto-saved prior to being manually saved
Submitted:	2 Apr 2015 6:43	Modified:	29 Nov 2015 9:23
Reporter:	Bacil Warren	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	6.2.5.0 Build 397	OS:	MacOS (10.10.2)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Workbench 6.2.5.0:
Created a new Model file, and created EER within file. Worked on file for a while, and then MySQL Workbench crashed prior to my being able to save the file.

Now, with the recovered file open, it cannot be saved to any location, even using "Save As …" command, and instead shows the following error:

Could not save XML data to file [redacted user path]/Library/Application Support/MySQL/Workbench/newmodel.mwbd/document.mwb.xml

Expected behavior: while this might be an appropriate error if the file is being Saved (although, it shouldn't, since I am still the owner of the directory the auto-recover document is stored in), it should *not* affect "Save As", since the file *should* be a new copy of the document. It does not appear to matter where the "Save As" is being directed (i.e., trying different directories, or even trying to "Save As" to an external HDD, does not change the behavior or the error message).

Also, I would expect the error to reflect the attempted save location, instead of the path of the auto-saved Model file.

How to repeat:
Since it's being formed by a crash of the application, I don't have any repeatability information. The next time it crashes, if I have an unsaved Model file open, I'll test that one, too.

Suggested fix:
Not a fix suggestion, but it seems reasonable to conclude there might be an error in the save logic, in that it's not actually attempting to save a new copy of the document to the user-selected location, but is instead attempting to re-save the currently open auto-save document, which will probably always fail?

Please try version 6.3.3. 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".

Hi
I faced a similar problem.
the best solution is, make changes to your EER, do a forward engg
once the db is created, delete the previous model file, and from the db, do a reverse engg
You will get your EER diagram and model file and then you can do further changes and re-save that model.

Please check 6.3.5. 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".