| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Cedar Cox <cedarc(at)visionforisrael(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Re: [HACKERS] triggered data change violation |
| Date: | 2001-03-20 21:15:09 |
| Message-ID: | 200103202115.QAA16953@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Sawtell | 2001-03-20 21:41:44 | Re: More on elog and error codes |
| Previous Message | Tom Lane | 2001-03-20 21:14:03 | Re: [HACKERS] triggered data change violation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-20 21:16:16 | Re: Re: Use of the LIMIT clause ? |
| Previous Message | Tom Lane | 2001-03-20 21:14:03 | Re: [HACKERS] triggered data change violation |