Tom Lane writes:
> Cedar Cox <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] http://yi.org/peter-e/
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
