From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rolf A. de By <deby@itc.nl>
Cc: pgsql-sql@postgresql.org
Subject: Re: Trigger definition . . . puzzled
Date: Thu, 13 Dec 2007 10:49:32 -0500
Message-ID: <12289.1197560972@sss.pgh.pa.us> (raw)
In-Reply-To: <4760DCED.7080805@itc.nl>
References: <4760DCED.7080805@itc.nl>
"Rolf A. de By" <deby@itc.nl> writes:
> Thanks for that. There is some misunderstanding here. For this example,
> I had taken the sting out of my trigger function and turned it into a
> much more concise no-op, with warnings. The actual code of my original
> trigger function is irrelevant. The no-op trigger function displays the
> same strange behaviour: it works as expected for INSERTs, but not for
> UPDATEs. The update goes through! And it shouldn't.
Reading between the lines, I gather you have an inheritance setup and
are expecting a trigger on the parent table to fire for events occurring
in the child tables. Doesn't work like that; you need to put triggers
on the child tables.
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, deby@itc.nl
Subject: Re: Trigger definition . . . puzzled
In-Reply-To: <12289.1197560972@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