Toad World® Forums

Self-referencing relationship creates duplicate column names


If a client can have a parent, the client table can reference itself. The translation from logical-to-physical creates a client table with two clientKey columns. One of them needs to be renamed.

I don’t see where this can be described in the relationship object. Should it be changed in the physical model or is there something I’m missing?



In this situation you can either map the FK or rename the attribute.
Please see the Help file | Index tab and type:

  • ‘fk mapping’
  • ‘rolename’ - to see how to rename the attribute.

If you have any questions, please write me back. Thanks.




Both of those appear to be physical-model only solutions. The problem with attribute naming would, I think, exist on the logical side as well. If a single logical design may be generated into more than one physcial design, it seems unfortunate to have to modify the design twice.



Yes, the options work for PER model only.
We’re sorry, we have no better solution for you at the moment - you have to make the modifications in PER model again.

Nevertheless, we will see what we can do about it. CR # 60 689.



Vladka + TDM Team