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(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Surrogate keys (Was: enums)
Date: 2006-01-19 06:46:32
Message-ID: 87bqy8ww8n.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


> >> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2006-01-19 06:56:51 Re: No heap lookups on index
Previous Message Tony Caduto 2006-01-19 06:18:45 Re: PostgreSQL Top 10 Wishlist

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2006-01-19 06:56:51 Re: No heap lookups on index
Previous Message Tom Lane 2006-01-19 06:45:58 Indexes vs. cache flushes