Bug #26910 | Odd handling of saving project with same name as an already existing project | ||
---|---|---|---|
Submitted: | 7 Mar 2007 9:52 | Modified: | 27 Oct 2009 9:47 |
Reporter: | Heinz Schweitzer (Gold Quality Contributor) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 5.2 | OS: | Windows (XP) |
Assigned to: | CPU Architecture: | Any | |
Tags: | CHECKED |
[7 Mar 2007 9:52]
Heinz Schweitzer
[7 Mar 2007 10:48]
Sveta Smirnova
Thank you for the report. Verified as described.
[15 Oct 2009 8:27]
Susanne Ebrecht
It needs to be checked if this is still true in Workbench 5.2.
[27 Oct 2009 9:33]
Susanne Ebrecht
Outsch .... Testing with Workbench 5.2: 1) Open Workbench 2) New Model 3) Add Diagram 4) Place a table with two columns 5) Save Model and name it foo.mwb 6) Close Workbench 7) Open Workbench 8) New Model 9) Add Diagram 10) Place a table without columns 11) Save Model and name it foo.mwb No warning happened. Nothing. No hint that foo.mwb already exist. No question if it should get overwritten or not. It just will get overwritten and all data from the original foo.mwb are gone away. That is very dangerous. Usually there should happen a popup that foo.mwb already exist and the question if you want to overwrite it or not.
[27 Oct 2009 9:47]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't fix this anymore in MySQL Administrator and for the Workbench problem I opened a separate bug #48345 More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/