Re: IS it a good practice to use SERIAL as Primary Key?

From: John McCawley <nospam(at)hardgeus(dot)com>
To: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: IS it a good practice to use SERIAL as Primary Key?
Date: 2006-11-27 21:04:01
Message-ID: 456B52C1.20702@hardgeus.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Right, but when you write your script (or whatever) that cleans these
keys up and does the merge, you're where you started -- arbitrary
integer keys with no meaning. If you merge databases where the keys are
*supposed* to have meaning, you then have to mangle *real* data to make
them merge.

Ron Johnson wrote:

>OK, let's use a synthetic key on the sales master table. In fact,
>*both* companies have a synthetic key on their sales master tables.
>
>OMG, conflicting/overlapping synthetic keys!!!!!
>
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2006-11-27 21:05:59 backend crash following load command
Previous Message Scott Ribe 2006-11-27 21:03:25 Re: IS it a good practice to use SERIAL as Primary Key?