Re: Data type to use for primary key

From: Alexandre Leclerc <alexandre(dot)leclerc(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Data type to use for primary key
Date: 2004-11-22 23:26:00
Message-ID: 1dc7f0e304112215265f6ba487@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Mr Caillaud,

Merci! Many points you bring were also my toughts. I was asking myself
really this was the way to go. I'm happy to see that my view of the
problem was good.

Encore merci! (Thanks again!)

On Tue, 23 Nov 2004 00:06:13 +0100, Pierre-Frédéric Caillaud
<lists(at)boutiquenumerique(dot)com> wrote:
>
> > 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.
>
> Use a serial :
> - you can change product_code for a product easily
> - you can pass around integers easier around, in web forms for instance,
> you don't have to ask 'should I escape this string ?'
> - it's faster
> - it uses less space
> - if one day you must manage products from another source whose
> product_code overlap yours, you won't have problems
> - you can generate them with a serial uniquely and easily
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

--
Alexandre Leclerc

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2004-11-23 00:54:56 Re: Data type to use for primary key
Previous Message Pierre-Frédéric Caillaud 2004-11-22 23:15:26 Re: scalability issues on win32