Re: Artificial Primary keys
Date: 24 Jan 2002 06:24:30 -0800
Message-ID: <c69419da.0201240624.62e1ed29_at_posting.google.com>
nsouto_at_optushome.com.au.nospam (Nuno Souto) wrote in message news:<3c4ebac6.7497784_at_news-vip.optusnet.com.au>...
>
> This happens mostly because no one is perfect like a computer, and
> data entry errors are made. And people need to be able to change an
> existing id/stdate without having to delete/re-create all info for an
> employee. Which is what they'd need to do if we made id+stdate the
> PK.
>
Nounu,
The point about needing to change the PK is taken; don't you think
this can be handled by cascading the changes to all the foreign keys?
Or have I misunderstood "cascading"? (As far as these "Assignments"
are concerned, there are over-riding business rules prohibiting
changes to PK, once their status moves from "Planned" to "Actual").
Regards and thanks for your reply,
Michael