From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cedar Cox <cedarc@visionforisrael.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: triggered data change violation
Date: Tue, 20 Mar 2001 13:13:53 -0500
Message-ID: <11744.985112033@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0103202033230.25524-100000@nanu.visionforisrael.com>
References: <Pine.LNX.4.21.0103202033230.25524-100000@nanu.visionforisrael.com>
Cedar Cox <cedarc@visionforisrael.com> writes:
> ERROR: triggered data change violation on relation "tblstsc2options"
> What is this? It doesn't happen unless I'm in a transaction. I'm
> INSERTing a record and then DELETEing it (in the same transaction) and on
> delete I get this error.
That's exactly what it's unhappy about ... but I'm not too clear on
just *why* that should be considered an uncool thing to do when you
have an AFTER trigger on the table. You're asking in the wrong list
though; try pgsql-hackers or pgsql-sql to see if someone knows why
this is bad.
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-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, cedarc@visionforisrael.com
Subject: Re: triggered data change violation
In-Reply-To: <11744.985112033@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