On 15 Apr 2002 at 14:20, Nick Fankhauser wrote:
> As a general rule, a primary key (or any relationship key) should not
> contain a value that means something beyond its use in relating entities.
> The problem is that if a field describes an object, the day may come when
> you want to change the
OTECTED]>
Sent: Monday, April 15, 2002 1:56 PM
Subject: [ADMIN] string PK vs. interger PK
Can anyone offer some insight as to what should be considered when choosing
between a primary key that is an integer vs. a primary key that is a string
value? Does one or the other affect indexing speed? up
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jodi Kanter
Sent: Monday, April 15, 2002 1:56 PM
To: Postgres Admin List
Subject: [ADMIN] string PK vs. interger PK
Can anyone offer some insight as to what should be considered when choosing
between a primary key that is an integer vs.
Can anyone offer some insight as to what
should be considered when choosing between a primary key that is an integer vs.
a primary key that is a string value? Does one or the other affect indexing
speed? update speed?
Is a serial integer value better than using a
PK that has some "value" in
