Re: Surrogate Keys: an Implementation Issue

Paul Mansour wrote:
> paul c wrote:
>
> > A system-supplied CANDIDATE key seems no more a bad conclusion than a
> > system-supplied date but I suspect there are readers here who would
> > prefer to complicate the environment by dragging in various code
> > standards or other arbitrary inventions. TTM suggests this very thing
> > in its 'RM strong suggestions' and can be found online although the book
> > goes into more detail and IIRC avoids using the to me risky word
> > 'super'. It also doesn't pre-suppose a '32-bit' value - eg., that
> > could have wrap-around problems. Maybe it's another argument for always
> > using views at the application level.

I forgot to add that 'super primary key' and '32-bit' value were thrown inadvisedly into my original post. Both of these are of course implemention issues, and the Relational Model would certainly be silent on both the concept of an immutable, unexposed identifier and whether or not it should be a 64 bit int or what have you. Received on Wed Jul 19 2006 - 19:06:03 CEST