Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2KLE4H97412; Tue, 20 Mar 2001 16:14:04 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2KLE3t12807; Tue, 20 Mar 2001 16:14:03 -0500 (EST) To: Cedar Cox cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [HACKERS] triggered data change violation In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Tue, 20 Mar 2001 23:55:25 +0200" Date: Tue, 20 Mar 2001 16:14:03 -0500 Message-ID: <12804.985122843@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/397 X-Sequence-Number: 2065 Cedar Cox 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