Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6NFQrf12138 for ; Mon, 23 Jul 2001 11:26:53 -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 89764; Mon, 23 Jul 2001 08:26:50 -0700 From: "Josh Berkus" Subject: Re: Re: Records exactly the same. To: "Fons Rave" Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 23 Jul 2001 08:26:50 -0700 Message-ID: In-Reply-To: <9jbrpj$r67$1@news1.xs4all.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===89764====davinci.ethosmedia.com===_" X-Archive-Number: 200107/312 X-Sequence-Number: 4120 This is a multi-part MIME message --_===89764====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Fons, > Well, I started with "I'm a beginner". But I'm sure there's no reason > NOT to > accept two records that are exactly the same. In the example I gave, > it is clear > that the information I want to store can contain two records that are > exactly > the same; doing the same thing, on the same day, for the same amount > of time. In > this case it is the technical structure that doesn't want it like > that. So I > have to change it to make it work. Yes, there is a reason not to accept them. And the requirement is conceptual, not technical -- that is, the way relational databases work -- *all* relational databases -- is founded on 12 concepts, one of which is the uniqueness of relations (records). Or, to phrase it another way, if your design allows identical records (person, task, time period) then how are *you* going to seperate illegitimate duplicate data-entry from legitimate identical records? You can't, and the questionable accuracy of your tables will haunt you for years. I'm trying to save you months of pain & suffering here by conveying a very important concept in database design, one I learned the hard way. For a more exhaustive explanation of the necessity of uniqueness and primary keys, please pick up a copy of Fabian Pascal's "Practical Issues in Database Design." -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 --_===89764====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89764====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89764====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89764====davinci.ethosmedia.com===_--