From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Cedar Cox <cedarc@visionforisrael.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Re: [HACKERS] triggered data change violation
Date: Tue, 20 Mar 2001 16:15:09 -0500 (EST)
Message-ID: <200103202115.QAA16953@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0103202210120.1639-100000@peter.localdomain>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, peter_e@gmx.net, tgl@sss.pgh.pa.us, cedarc@visionforisrael.com, pgsql-hackers@postgresql.org
Subject: Re: Re: [HACKERS] triggered data change violation
In-Reply-To: <200103202115.QAA16953@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox