Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f72Ma8f34495 for ; Thu, 2 Aug 2001 18:36:08 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 95984; Thu, 02 Aug 2001 15:36:03 -0700 From: "Josh Berkus" Subject: Re: More Database Design Stuff To: "Chris Ruprecht" , "pgsql" X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Thu, 02 Aug 2001 15:36:03 -0700 Message-ID: In-Reply-To: <009301c11b96$0b744c60$5dd26383@corp.compucom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200108/22 X-Sequence-Number: 4243 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@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco