Re: [HACKERS] triggered data change violation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cedar Cox <cedarc(at)visionforisrael(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [HACKERS] triggered data change violation
Date: 2001-03-20 20:39:53
Message-ID: 12536.985120793@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-20 21:10:21 Re: Final Call: RC1 about to go out the door ...
Previous Message Bruce Momjian 2001-03-20 20:32:44 Re: Allowing WAL fsync to be done via O_SYNC

Browse pgsql-sql by date

  From Date Subject
Next Message Cedar Cox 2001-03-20 21:13:14 triggered data change violation
Previous Message Bruce Momjian 2001-03-20 20:21:29 Re: Re: Use of the LIMIT clause ?