X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id ADED347580B
	for <pgsql-sql@postgresql.org>; Sat, 26 Apr 2003 00:21:06 -0400 (EDT)
Received: from davinci.ethosmedia.com (unknown [209.10.40.251])
	by postgresql.org (Postfix) with ESMTP id 3C842474E42
	for <pgsql-sql@postgresql.org>; Sat, 26 Apr 2003 00:21:03 -0400 (EDT)
Received: from [63.195.55.98] (HELO spooky)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 2989507; Fri, 25 Apr 2003 21:21:05 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Jan Wieck <JanWieck@Yahoo.com>,
	Andreas Pflug <Andreas.Pflug@web.de>
Subject: Re: Statement triggers 7.4 NEW/OLD
Date: Fri, 25 Apr 2003 21:20:01 -0700
User-Agent: KMail/1.4.3
Cc: pgsql-sql@postgresql.org
References: <3EA7CD6A.9080404@web.de> <3EA9EFA3.EF4C0D1@Yahoo.com>
In-Reply-To: <3EA9EFA3.EF4C0D1@Yahoo.com>
MIME-Version: 1.0
Message-Id: <200304252120.01644.josh@agliodbs.com>
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200304/390
X-Sequence-Number: 13091

Jan,

> 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.

Yeah; how else could it possibly work?

--=20
Josh Berkus
Aglio Database Solutions
San Francisco