Re: primary key and existing unique fields - Mailing list pgsql-general

From Duane Lee - EGOVX
Subject Re: primary key and existing unique fields
Date
Msg-id 2173F8FD02F0A443BF578E975AF3C793195BC3@EVS2.enterprise.maricopa.gov
Whole thread Raw
In response to primary key and existing unique fields  ("Sally Sally" <dedeb17@hotmail.com>)
List pgsql-general

Since you already have the unique field I see no point in adding a sequence to the table, unless of course the sequence of the data inserts is of importance at some point.

Duane

-----Original Message-----
From: Sally Sally [mailto:dedeb17@hotmail.com]
Sent: Tuesday, October 26, 2004 9:25 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] primary key and existing unique fields

Hi all,
I am wandering about the pros and cons of creating a separate serial field
for a primary key when I already have a single unique field. This existing
unique field will have to be a character of fixed length (VARCHAR(12))
because although it's a numeric value there will be leading zeroes. There
are a couple more tables with similar unique fields and one of them would
need to reference the others. Does anybody see any good reason for adding a
separate autoincrement primary key field for each table? or either way is
not a big deal.
Sally

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

pgsql-general by date:

Previous
From: "Sally Sally"
Date:
Subject: primary key and existing unique fields
Next
From: "Joshua D. Drake"
Date:
Subject: Re: primary key and existing unique fields