From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres, DB design, and object IDs (of any ilk) |
Date: | 2009-05-21 21:38:05 |
Message-ID: | 874ove87cy.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
kentilton(at)gmail(dot)com (Kenneth Tilton) writes:
> Just looking for postgres "best practices" input from the veterans:
OIDs are decidedly a bad idea; the difference between "natural" IDs
and "surrogate" IDs is a general database issue that is fairly well
documented in the literature and is not notably a PostgreSQL-specific
issue.
There are competing doctrines, basically between the respective
beliefs:
a) Some believe that there should always be a natural primary key,
and that it is wrong to attempt to use surrogates
b) Others contend that even when users claim to provide natural
primary keys that they are actually lying when they suggest
certainty about this
Major bashing can take place back and forth.
--
output = ("cbbrowne" "@" "acm.org")
http://cbbrowne.com/info/wp.html
Rules of the Evil Overlord #100. "Finally, to keep my subjects
permanently locked in a mindless trance, I will provide each of them
with free unlimited Internet access. <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Timmy | 2009-05-21 22:26:22 | Re: Re: Can not decompress a compressed string under plpy! |
Previous Message | Karl Nack | 2009-05-21 20:50:18 | Re: After each row trigger NOT seeing data changes? |