Bug #53020 ambiguous foreign key identifiers after copy table
Submitted: 21 Apr 2010 9:28 Modified: 4 May 2010 10:43
Reporter: Michael Schramm Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.16 beta, 5.2.19 OS:Windows (Windows 7)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: ambiguous identifiers, copy table, foreign key

[21 Apr 2010 9:28] Michael Schramm 
Description:
If you copy a table the table with foreign keys, the table will be renamed "copy_old_tablename" but all foreign key identifiers stays the same!

That causes massive problem in forward engineering as the foreign keys must have an unique identifier.

Even ambiuougos tablennames must disalowed in the EER environment.

How to repeat:
?
[21 Apr 2010 9:37] Valeriy Kravchuk 
Thank you for the problem report. Verified just as described with 5.2.19 on Windows XP.
[21 Apr 2010 12:29] Michael Schramm 
i just  updated the OS

and use java 6 with Update 20

Kind Regards from Berlin
[30 Apr 2010 19:25] Johannes Taxacher 
fix confirmed in repository
[4 May 2010 10:43] Tony Bedford 
An entry has been added to the 5.2.21 changelog:

If a table was copied in the modeler, the copy of the table was renamed. However, foreign key relationships contained within the table were not renamed.