From: | Cedar Cox <cedarc(at)visionforisrael(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:55:25 |
Message-ID: | Pine.LNX.4.21.0103202348570.27436-100000@nanu.visionforisrael.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Tue, 20 Mar 2001, Tom Lane wrote:
> 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?
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,
PRIMARY KEY (SC2OptionID)
);
And there is one other table, tblListRequestSentItems, which has a field:
SC2OptionID int4 DEFAULT 0 NOT NULL REFERENCES tblStSC2Options,
Have I answered your question? (I think so.)
-Cedar
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Ansley | 2001-03-20 22:03:26 | RE: Final Call: RC1 about to go out the door ... |
Previous Message | Rosie Sedghi | 2001-03-20 21:50:05 |
From | Date | Subject | |
---|---|---|---|
Next Message | Najm Hashmi | 2001-03-20 22:04:24 | Postgres & XML |
Previous Message | Bruce Momjian | 2001-03-20 21:19:20 | Re: Re: Use of the LIMIT clause ? |