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-k
> 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 probl
