MySQL Bugs: #20468: Adding 2nd 1:n diuplicates other existing 1:n

Bug #20468	Adding 2nd 1:n diuplicates other existing 1:n
Submitted:	14 Jun 2006 18:08	Modified:	3 Sep 2006 3:21
Reporter:	Kael Fischer	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S2 (Serious)
Version:	1.0.6 beta	OS:	Linux (Linux/Windows)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Existing relationshis and foriegn keys are duplicated on screen when adding 1:n relationships after the first 1:n. 

Note that if the duplicate relationship is deleted and the model is save and reloaded, readding the relationship doesn't work.

How to repeat:
Start with new schema.
Create 3 new InnoDB tables: parent1, parent2, child.
Create primary keys for the talbes.
Use the 1:n tool to make a relationship (1:n) between parent1:child.
Use the 1:n tool to make a relationship (1:n) between parent2:child.

The first relationship is now present in 2 copies.
 

Suggested fix:
The robust behavior I got used to in DBDesigner4 would be a big improvment.

The bug description says that the FS's are duplicated, but the are not.  Only the relationship is duplicated.

Thank you for the bug report.

This also happens when you create additional 1-n relationships on tables NOT involved in the initial relationship.

When I created two tables and a relationship between them, an appropriate FK relationship was displayed. Then I added columns to one of the tables involved in the relationship, and for each of the columns added, a new relationship was created on the diagram (between tables test_defn and feature).

Additionally, when I attempted to duplicate this behavior by creating two other tables in the same schema, foo and bar, which are NOT involved in the test_defn->feature releationship, MySQL Workbench added even MORE of these relationships (3, to be exact) between tables test_defn and feature after adding a 1-n relationship between foo and bar.

Then, when I added attrib2 and attrib3 to table foo, MySQL Workbench added ANOTHER relationship between test_defn and feature (now totaling 7), and duplicated the existing relationship between foo and bar (now totalling 2).

I have screenshot for clarification if you want it since it seems I can't attach one here.

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/