Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3PLgT301757 for ; Wed, 25 Apr 2001 17:42:30 -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 44183; Wed, 25 Apr 2001 14:42:26 -0700 From: "Josh Berkus" Subject: Re: Error explaination? To: Jan Wieck , Josh Berkus Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Wed, 25 Apr 2001 14:42:26 -0700 Message-ID: In-Reply-To: <200104252117.QAA30608@jupiter.jw.home> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200104/390 X-Sequence-Number: 2748 Jan, Thanks for the quick response. > This is a known misbehaviour (not to call it a bug) that we > keep since having deferrable referential integrity. Some sort of "catch 22" I take it? Am I correct in understanding that my choices are to: a) do something other than deleting the records, or b) drop the referential integrity check on the table? -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