Re: Data type to use for primary key

Поиск
Список
Период
Сортировка
От Rod Taylor
Тема Re: Data type to use for primary key
Дата
Msg-id 1101171791.44437.7.camel@home
обсуждение исходный текст
Ответ на Re: Data type to use for primary key  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Data type to use for primary key  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-performance
On Mon, 2004-11-22 at 16:54 -0800, Josh Berkus wrote:
> Alexandre,
>
> > What is the common approach? Should I use directly the product_code as
> > my ID, or use a sequantial number for speed? (I did the same for the
> > company_id, this is a 'serial' and not the shor name of the customer.
> > I just don't know what is usually done.
>
> Don't use SERIAL just because it's there.    Ideally, you *want* to use the
> product_code if you can.   It's your natural key and a natural key is always
> superior to a surrogate key all other things being equal.

It would be nice if PostgreSQL had some form of transparent surrogate
keying in the background which would automatically run around and
replace your real data with SERIAL integers. It could use a lookup table
for conversions between the surrogate and real values so the user never
knows that it's done, a bit like ENUM. Then we could all use the real
values with no performance issues for 1) because it's an integer in the
background, and 2) because a cascade only touches a single tuple in the
lookup table.


--


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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Data type to use for primary key
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: memcached and PostgreSQL