Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46] (may be forged)) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2KLGVH97771; Tue, 20 Mar 2001 16:16:31 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id QAA16953; Tue, 20 Mar 2001 16:15:09 -0500 (EST) From: Bruce Momjian Message-Id: <200103202115.QAA16953@candle.pha.pa.us> Subject: Re: Re: [HACKERS] triggered data change violation In-Reply-To: "from Peter Eisentraut at Mar 20, 2001 10:13:35 pm" To: Peter Eisentraut Date: Tue, 20 Mar 2001 16:15:09 -0500 (EST) CC: Tom Lane , Cedar Cox , pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/398 X-Sequence-Number: 2066 > A "triggered data change violation" happens everytime you change twice > within a transaction a value (column) that is part of a foreign key > constraint (don't recall exactly which part). > > This error shouldn't really happen, but I recall there were some > implementation and definition problems with deferred constraints. > > ...FAQ alert... Yes, I just got it in the TODO list a few weeks ago: * INSERT & UPDATE/DELETE in transaction of primary key fails with deferredTriggerGetPreviousEvent or "change violation" [foreign] I personally think we could do better on the wording of that error message, at least until we get it fixed. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026