Re: Statement triggers 7.4 NEW/OLD

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Statement triggers 7.4 NEW/OLD
Date: 2003-04-26 02:32:03
Message-ID: 3EA9EFA3.EF4C0D1@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Jan Wieck 2003-04-26 02:47:54 Re: /* */ comments showing up in pg_stat_activity
Previous Message Tom Lane 2003-04-26 02:18:34 Re: create/alter/drop within transactions?