Message-ID: <3EA9EFA3.EF4C0D1@Yahoo.com>
Date: Fri, 25 Apr 2003 22:32:03 -0400
From: Jan Wieck <JanWieck@Yahoo.com>
Organization: Home
MIME-Version: 1.0
To: Andreas Pflug <Andreas.Pflug@web.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Statement triggers 7.4 NEW/OLD
References: <3EA7CD6A.9080404@web.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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 #