From: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
---|---|
To: | John McCawley <nospam(at)hardgeus(dot)com>, 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 19:37:11 |
Message-ID: | C1908C77.5C25D%scott_ribe@killerbytes.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> In the real world,
> data changes, even supposedly unchangeable data.
And that's the crux of it. All of the "that design is wrong" arguments in
the world won't stop data that has been constant & unique for decades from
changing when some manager, rightly or wrongly, sees a "business need" for
it. User-provided data can never, ever be counted on to forever and always
have the attributes (uniqueness, stability, whatever) described by the
users, no matter how many times you are reassured on the subject. The data
will very often behave exactly as described, but to base a database design
on that assumption is to create a brittle design--as you described.
--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-11-27 19:38:51 | Re: fatal error on 8.1 server |
Previous Message | Tony Caduto | 2006-11-27 19:36:02 | Re: fatal error on 8.1 server |