Message-ID: <478DCCA1.4060505@archonet.com>
Date: Wed, 16 Jan 2008 09:21:37 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: Gerardo Herzig <gherzig@fmed.uba.ar>
CC: "pgsql-sql@postgresql.org" <pgsql-sql@postgresql.org>
Subject: Re: obtaining the query string inside a trigger
References: <478D25B7.8030308@fmed.uba.ar>
In-Reply-To: <478D25B7.8030308@fmed.uba.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Gerardo Herzig wrote:
> Hi all. Im working on a "on each statement" update trigger, so NEW and 
> OLD are NULL.
> Suppose a simple query like 'update mytable set id=id+500 where id < 
> 50'...There is a way to obtaining the 'set id=..' and the where clause
> in some way?

Afraid not. It might be possible to implement in the simple case, but 
what with views rewriting queries and triggers issuing their own 
secondary queries it's not always obvious what "the" query would be.

What we really need is NEW and OLD as sets of affected rows in 
statement-queries. Unfortunately that's not implemented yet either - 
it's on the TODO I believe though.

-- 
   Richard Huxton
   Archonet Ltd