Duplicated FK names when cloning tables with references.
aalejandro 4 years ago • updated by chris hynes 2 years ago • 6 • 2 duplicates
When a table with foreign keys references (FK) is cloned using the functionality provided in the context menu, the new cloned table sets the same name to the reference. At design time there's no issue but when you create the forward engineering script it will fail when you execute it on the database.
Customer support service by UserEcho
We are looking into this issue. We will notify you as soon as we know more details.
Team - SqlDBM
I am experiencing this same issue. I have cloned tables, and they are fine in the design editor, but when I forward engineer, the cloned table has the Constraint name defaulted to the original table constraint name. I have gone into the designer to provide a valid name for the primary key constraint, but it seems to hold on to the original constraint name for the original table. This is a huge issue for me. I don't know how many tables I have cloned, and now at run time, I am have to manually repair all of these constraint names. Please fix asap.
Sorry for the inconvenience.
Agree, we need to fix this constraint naming when cloning a table.
But this is very strange, that even after manually fixing the PK name of the cloned table in the designer, it does not hold new value.
Can you please elaborate, what exactly happens when you try to save the new name: Does it change to original PK name automatically OR the SQL generated is not as expected?
Maybe can you please share screenshot of the issue, so we can better investigate the issue.
Team - SqlDBM
It saves successfully and is visible. But when I forward engineer the table, the generated script still refers to the old namr
I am also having this issue
Thank you for the report, good point, we will work on it