Skip site navigation (1) Skip section navigation (2)

Re: plpython triggers TD["new"] = None

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Lee Jensen <ljensen(at)carriersales(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: plpython triggers TD["new"] = None
Date: 2005-01-27 23:11:50
Message-ID: 20050127231150.GB27963@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, Jan 27, 2005 at 04:01:32PM -0700, Michael Fuhr wrote:
> On Thu, Jan 27, 2005 at 07:46:54PM -0300, Alvaro Herrera wrote:
> > On Thu, Jan 27, 2005 at 03:34:55PM -0700, Michael Fuhr wrote:
> > 
> > > OLD and NEW don't make sense in statement-level triggers because
> > > the statement could affect many rows.  Use FOR EACH ROW if you need
> > > to access the row values.
> > 
> > IMHO they do make sense.  It's just that they haven't been implemented.
> 
> What do you have in mind?  What would OLD and NEW refer to in
> statements that affect multiple rows?  Are you thinking of a way
> to refer to all of the old and new rows?

Yes, exactly that.  They would be arrays of tuples (or whatever they are
called in Python -- I'm not thinking specifically in Python.)

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Escucha y olvidarás; ve y recordarás; haz y entenderás" (Confucio)

In response to

Responses

pgsql-bugs by date

Next:From: Michael FuhrDate: 2005-01-27 23:23:10
Subject: Re: plpython triggers TD["new"] = None
Previous:From: Michael FuhrDate: 2005-01-27 23:01:32
Subject: Re: plpython triggers TD["new"] = None

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group