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 21:14:03
Message-ID: 12804.985122843@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:
>> 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?

> Not any that I wrote. Ok, the table def is:

> CREATE TABLE tblStSC2Options (
> SC2OptionID int4 NOT NULL,
> SC2OptionName character varying(50) NOT NULL CHECK (SC2OptionName<>''),
> SC2OptionValue float4 CHECK (SC2OptionValue>0),
> SurID character varying(50) NOT NULL REFERENCES tblStSC2 ON UPDATE
> CASCADE ON DELETE CASCADE,
^^^^^^^^^^^^^^^^^^^

Sure looks like a foreign key to me. If you dump the table definition
with pg_dump you'll see some AFTER triggers.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-20 21:15:09 Re: Re: [HACKERS] triggered data change violation
Previous Message Peter Eisentraut 2001-03-20 21:13:35 Re: [HACKERS] triggered data change violation

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2001-03-20 21:15:09 Re: Re: [HACKERS] triggered data change violation
Previous Message Peter Eisentraut 2001-03-20 21:13:35 Re: [HACKERS] triggered data change violation