- SqlDBM Forum
-
Ideas
How do I add an FK to an existing column
I've imported an existing schema that didn't have any FK's set, but all of the columns are there ready for the FK.
So, how can i add a new FK for the PK of the parent table to the existing column in the child table.
At the moment I have to delete the column and add the FK, otherwise it adds the column in again with a "_1" suffix.
Thanks
Andrew
Answer
To connect two table, tool creates new FK column in child table, this is done deliberately to avoid any mistakes by the user. Otherwise there are lot of chances of mistake, like not all the properties/attributes of the column be same. For example if Parent column PK is of datatype nvarchar(45), and child table column (which user wants to make as FK) is nvarchar(46).
Probably, in future we will add the feature where when user tries to add relationship, and the tool finds same column in child table with same properties/attributes, then use existing column.
For now, just delete the column and create relationships, which makes sure that new FK column has correct attributes.
Thanks
Team - SqlDBM
In my opinion, it should have been there out of the box. In my case, I imported my schema and was trying to add new FKs to an existing table. It should be the user's decision. UI could prompt a warning about it before adding/editing.
This should be re-prioritised urgently. It's entirely appropriate to modify existing schema.
I agree, we should have the freedom to allocate keys and generate relationships manually. If you would like to avoid errors or mistakes you could build a module that could then cross check the schema at the Users request
this "feature" renders this tool unusable, in my opinion. I've laid out all my tables and now I can't tie them together without turning the erd into a huge mess. I guess I'll look elsewhere.
Customer support service by UserEcho
To connect two table, tool creates new FK column in child table, this is done deliberately to avoid any mistakes by the user. Otherwise there are lot of chances of mistake, like not all the properties/attributes of the column be same. For example if Parent column PK is of datatype nvarchar(45), and child table column (which user wants to make as FK) is nvarchar(46).
Probably, in future we will add the feature where when user tries to add relationship, and the tool finds same column in child table with same properties/attributes, then use existing column.
For now, just delete the column and create relationships, which makes sure that new FK column has correct attributes.
Thanks
Team - SqlDBM