On 11/15/06, Powell, Mark D <mark.powell_at_eds.com> wrote:
>
>
> When the UK is built on a business value that needs to be carried in the
> child table and the PK of the parent is an artificial key is one
> situation where this may happen.
>
>
Doing so would seem to indicate that the values of the UK may change
over time. If you do this, you need to take it into account in the
application.
If the UK is going to be used as a PK, I think it would be better just
to make it the PK to start with, as it would be less confusing.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Nov 15 2006 - 12:34:26 CST
