From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: IS it a good practice to use SERIAL as Primary Key? |
Date: | 2006-11-27 17:47:07 |
Message-ID: | 1164649627.14565.24.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2006-11-23 at 10:23, Ron Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/22/06 20:23, carter ck wrote:
> > Hi all,
> >
> > I am wonderring if it is a good practice to use SERIAL index as primary
> > key, as it is only available up to 9999999?
> >
> > Currently i am dealing with storing LDAP users into Postgres and i am
> > looking for a better way to make use of the DN as primary key instead of
> > SERIAL index.
> >
> > Any advice or suggestion is appreciated.
>
> I'm one of those who thinks that a (possibly multisegment) natural
> key *does* exist, and that if you think it doesn't, your design is
> wrong.
Spend some time in the travel industry... The tax category ZO means
Passenger Service Chareg in Denmark. Or Greenland, or Faroe Islands.
And can be entered more than once. And the travel agent has to look at
the context of the travel itinerary to know which one(s) it is.
Sadly, the real world has many data problems created by idiots in suits
30 years ago that aren't going to go away any time soon.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-11-27 17:53:43 | Re: Linux hard drive/device nodes for a Postgres RAID |
Previous Message | Volkan YAZICI | 2006-11-27 17:28:57 | Re: Returning multiple rows from a function? |