Re: Surrogate keys (Was: enums)

Поиск
Список
Период
Сортировка
От Bruno Wolff III
Тема Re: Surrogate keys (Was: enums)
Дата
Msg-id 20060124095744.GB7766@wolff.to
обсуждение исходный текст
Ответ на Re: Surrogate keys (Was: enums)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Thu, Jan 19, 2006 at 00:06:41 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> The problem with SSN is that somebody other than you controls it.
> If you are the college registrar, then you control the student's
> registration number, and you don't have to change it.  In fact, guess
> what: you probably generated it in the same way as a surrogate key.

I work for a University and even the numbers assigned by us get changed on a
regular basis as it is very easy for people to get entered into the
system multiple times. (And for a while campus ids were SSNs by default and we
are still in the process of making them different for everyone.) There are
several effectively surrogate keys (campus id and emplid), but they don't map
1 to 1 to real people. I believe we keep a history of campus ids, and delete
emplids for duplicates.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "R, Rajesh (STSD)"
Дата:
Сообщение: Re: [GENERAL] [PATCH] Better way to check for getaddrinfo function.
Следующее
От: Bruno Wolff III
Дата:
Сообщение: Re: Surrogate keys (Was: enums)