Bug #53183 Save Model As performs opens a new document
Submitted: 27 Apr 2010 4:41 Modified: 28 Apr 2010 16:23
Reporter: Charles Whipple Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.19 OS:Windows (Windows 7, XP)
Assigned to: CPU Architecture:Any
Tags: Save Model As... opens new model

[27 Apr 2010 4:41] Charles Whipple
Description:
When I am performing a Save As on an EER diagram, it attempts to open a new diagram instead of saving the current one.  I checked and re-checked to make sure I click the [Save Model As] and not the Open Model, so I know I'm not just being clumsy with the mouse.  This is a pretty serious problem.  I worked around it by coping the actual file and then moving/renaming the copy.  Below is the sys info of my system. 

MySQL Workbench SE for Windows version 5.2.19
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.1.8787
OS: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
CPU: 8x Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz	�@	��@	��@	�Q�
@��Q�
, 4.0 GiB RAM
Video adapter info:
Adapter type: ATI Radeon HD 4800 Series
Chip Type: ATI display adapter (0x9442)
BIOS String: 113-B50107-100
Video Memory: 524288 KB

How to repeat:
Open a EER diagram.  Try to [Save Model As] a new document.  It will try to open one instead of saving.  

Suggested fix:
Looks like the [Save Model As] menu item is calling a routine to open a model instead.  Change the call to the save routine and all should be well.
[27 Apr 2010 6:01] Sveta Smirnova
Thank you for the report.

> When I am performing a Save As on an EER diagram, it attempts to open a new diagram
instead of saving the current one. 

Is it empty diagram in your case or this new diagram contains all objects from one you want to "Save As"?
[27 Apr 2010 6:02] Valeriy Kravchuk
Thank you for the bug report. Verified just as described on Windows XP.
[28 Apr 2010 16:23] Johannes Taxacher
this is a duplicate of Bug #52909