From: Jan Wieck <JanWieck@Yahoo.com>
To: Andreas Pflug <Andreas.Pflug@web.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Statement triggers 7.4 NEW/OLD
Date: Fri, 25 Apr 2003 22:32:03 -0400
Message-ID: <3EA9EFA3.EF4C0D1@Yahoo.com> (raw)
References: <3EA7CD6A.9080404@web.de>
Andreas Pflug wrote:
>
> How can I address the rows affected by an insert/update/delete statement
> in pl/pgsql?
> The doc says that NEW and OLD will be NULL for statement triggers, which
> makes sense because NEW and OLD are of type RECORD, capable of holding
> only a single row.
> So where's the beef?
IMHO statement triggers instead should have access to the NEW and OLD
rows through some mechanism. I can think of NEW and OLD being reference
cursors in the case of statement triggers, and the trigger then can
FETCH the rows from there.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
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: JanWieck@Yahoo.com, Andreas.Pflug@web.de
Subject: Re: Statement triggers 7.4 NEW/OLD
In-Reply-To: <3EA9EFA3.EF4C0D1@Yahoo.com>
* 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