Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Surrogate keys (Was: enums)
- From: Greg Stark <gsstark(at)mit(dot)edu>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>, "Dann Corbit" <DCorbit(at)connx(dot)com>, Leandro Guimarães Faria Corcete Dutra <leandro(at)dutra(dot)fastmail(dot)fm>, "Jim C. Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Surrogate keys (Was: enums)
- Date: 19 Jan 2006 01:46:32 -0500
- Message-id: <87bqy8ww8n.fsf@stark.xeocode.com> <text/plain>
> >> If a primary key exists for a collection that is known never to change, > >> for example social security number, student registration number, or > >> employee number, then no additional system-assigned UID is required. In point of fact Social security numbers *can* change. -- greg
- References:
- Re: FW: Surrogate keys (Was: enums)
- From: Dann Corbit
- Re: Surrogate keys (Was: enums)
- From: Michael Glaesemann
- Re: Surrogate keys (Was: enums)
- From: Tom Lane
- Re: FW: Surrogate keys (Was: enums)
- Prev by Date: Indexes vs. cache flushes
- Next by Date: Re: No heap lookups on index
- Previous by thread: Re: Surrogate keys (Was: enums)
- Next by thread: Re: Surrogate keys (Was: enums)
- Indexes: