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

[7 Mar 2007 9:52] Heinz Schweitzer
Odd handling of name changes of backup projects or in creating new projects

Changing the name of a backup project to an already existing project
will overwrite this project. 
Creating a new Project with a name of an existing project will also
overwrite the existing one.

These situations of name clashes are much better handled when creating a new user or schema,
or changing the name of users or schema.

MySQL Administrator 1.2.10

MySQL Server Information
Connected to MySQL Server Instance
  Username:                root
  Hostname:                localhost
  Port:                    3306
Server Information
  MySQL Version:           MySQL 5.0.27-community-nt via TCP/IP
  Network Name:            localhost
Client Information
  Version:                 MySQL Client Version 5.1.11
  Network Name:            xxxxxxxxxxx
  IP:                      xxxxxxxxxxx
  Operating System:        Windows XP
  Hardware:                2x Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz, 2.0 GB RAM

How to repeat:

Open MA
Create two new backup projects with name 'a' and 'b'
select backup  project 'a'.
Change the name from 'a' to 'b' and save project.

--> error dialog telling that a project 'b' already exists
--> project a no longer exists and project 'b' is overwritten by 'a'

Create a new project and give it  name  'b' then say Save Project.

--> error dialog telling that a project 'b' already exists
--> project 'b' is overwritten by whatever you specified in new project
[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: