From: | Duane Lee - EGOVX <DLee(at)mail(dot)maricopa(dot)gov> |
---|---|
To: | "'Sally Sally'" <dedeb17(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: primary key and existing unique fields |
Date: | 2004-10-26 16:46:15 |
Message-ID: | 2173F8FD02F0A443BF578E975AF3C793195BC3@EVS2.enterprise.maricopa.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)hotmail(dot)com]
Sent: Tuesday, October 26, 2004 9:25 AM
To: pgsql-general(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2004-10-26 16:48:50 | Re: primary key and existing unique fields |
Previous Message | Sally Sally | 2004-10-26 16:24:44 | primary key and existing unique fields |