From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cedar Cox <cedarc@visionforisrael.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [HACKERS] triggered data change violation
Date: Tue, 20 Mar 2001 16:14:03 -0500
Message-ID: <12804.985122843@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0103202348570.27436-100000@nanu.visionforisrael.com>
References: <Pine.LNX.4.21.0103202348570.27436-100000@nanu.visionforisrael.com>
Cedar Cox <cedarc@visionforisrael.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, cedarc@visionforisrael.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] triggered data change violation
In-Reply-To: <12804.985122843@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox