Re: identity columns

E-mail addresses are not good PKs. I've been at the same company for over 6 years, and I've had three different email addresses (long story, but legitimate reasons.)

"--CELKO--" <71062.1056_at_compuserve.com> wrote in message news:c0d87ec0.0201060830.610c4a90_at_posting.google.com...
> >> There seems to be a lot of talk in this NG about the good, bad and
> ugly
> aspects of primary keys - especially Identity columns. <<
>
> First, I would name the table "Personnel" and not "Employee" -- it is
> a set, so you want a plural or collective noun, not a singular
> (scalar) one. Next, I assume that you have a business rule that says
> everyone gets a company assigned email address when we hire them.
> Yes, I would use it; it has a beautiful property that an artifacial
> key does not -- you can verify it by sending out an email!! You know
> that they guy was fired if it bounces back to you, you can aks him his
> name, or whatever else you need to know. Next bst thing to putting
> the person themselves in the database.
>
Received on Mon Jan 07 2002 - 10:12:38 CST