| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Cedar Cox <cedarc(at)visionforisrael(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] triggered data change violation |
| Date: | 2001-03-20 21:13:35 |
| Message-ID: | Pine.LNX.4.30.0103202210120.1639-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Tom Lane writes:
> Cedar Cox <cedarc(at)visionforisrael(dot)com> writes:
> > Added note: The trigger is a BEFORE trigger.
>
> AFAIK the "triggered data change" message comes out of the AFTER trigger
> code. You sure you don't have any AFTER triggers on the table? Perhaps
> ones added implicitly by a foreign-key constraint?
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...
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-20 21:14:03 | Re: [HACKERS] triggered data change violation |
| Previous Message | Bruce Momjian | 2001-03-20 21:13:30 | Re: Performance monitor signal handler |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-20 21:14:03 | Re: [HACKERS] triggered data change violation |
| Previous Message | Cedar Cox | 2001-03-20 21:13:14 | triggered data change violation |