From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: Neil Conway <neilc@samurai.com>
Cc: Harald Fuchs <hf99@protecting.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Trigger question
Date: Tue, 20 Jan 2004 11:02:29 -0500
Message-ID: <24300.1074614549@sss.pgh.pa.us> (raw)
In-Reply-To: <200401200813.57147.dev@archonet.com>
References: <400691EA.96598C34@t1.unisoftbg.com>
<pud69kf3hr.fsf@srv.protecting.net>
<871xpvij42.fsf@mailbox.samurai.com>
<200401200813.57147.dev@archonet.com>
Richard Huxton <dev@archonet.com> writes:
> On Tuesday 20 January 2004 00:01, Neil Conway wrote:
>> Yeah, I didn't get around to implementing that. If anyone wants this
>> feature, I'd encourage them to step up to the plate -- I'm not sure
>> when I'll get the opportunity/motivation to implement this myself.
> I didn't think they'd be meaningful for a statement-level trigger. Surely
> OLD/NEW are by definition row-level details.
According to the complainants, OLD/NEW are commonly available as
recordsets (tables) inside a statement trigger. I'm not very clear on
how that works myself --- in particular, one would think it important to
be able to work with corresponding pairs of OLD and NEW rows, which
would be painful with a table-like abstraction. Can anyone explain
exactly how it's done in, say, Oracle?
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, dev@archonet.com, neilc@samurai.com, hf99@protecting.net
Subject: Re: Trigger question
In-Reply-To: <24300.1074614549@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