Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f6NDxBf66458 for ; Mon, 23 Jul 2001 09:59:11 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6LCVOa98313 for ; Sat, 21 Jul 2001 08:31:24 -0400 (EDT) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.4/8.11.4) id f6LCFoN35967 for pgsql-sql@postgresql.org; Sat, 21 Jul 2001 08:15:50 -0400 (EDT) (envelope-from news) From: "Fons Rave" X-Newsgroups: comp.databases.postgresql.sql Subject: Re: Records exactly the same. Date: Sat, 21 Jul 2001 14:15:26 +0200 Organization: XS4ALL Internet BV Lines: 16 Message-ID: <9jbrpj$r67$1@news1.xs4all.nl> References: X-Complaints-To: abuse@xs4all.nl X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 To: pgsql-sql@postgresql.org X-Archive-Number: 200107/305 X-Sequence-Number: 4109 > Well, there isn't an easy answer for you ... because you've designed > your database wrong. Records should *never* be the same. That is, ni > fact, one of the cardinal rules of Relational Database Design. 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. Fons. fonzzz@xs4all.nl