| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Chris Ruprecht" <chrup999(at)yahoo(dot)com>, "pgsql" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: More Database Design Stuff |
| Date: | 2001-08-02 22:36:03 |
| Message-ID: | web-95984@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Chris,
> I don't really care if people say it's bad to do this kind of thing,
> I like
> to tell them that I will do what works for me, and there is usually
> not much
> to argue about that point ;).
In most cases, simple surrogate keys (i.e. cust_id SERIAL) are the
easiest things to deal with. However, there are many cases where a
multi-column key can be superior.
Fabian Pascal has an excellent disussion of evaluating the suitability
of candidate keys in selecting a primary key in Practical Issues in
Database Design. It may also be on his web site
(http://www.firstsql.com/dbdebunk/)
(Candidate keys are unique combos of information in a table that could
be a primary key if you wanted)
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Morgan Curley | 2001-08-03 03:50:58 | converting timestamps to ints |
| Previous Message | Chris Ruprecht | 2001-08-02 20:59:38 | Re: More Database Design Stuff |