From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
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:23:10 |
Message-ID: | 20050127232310.GA47909@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Jan 27, 2005 at 08:11:50PM -0300, Alvaro Herrera wrote:
> On Thu, Jan 27, 2005 at 04:01:32PM -0700, Michael Fuhr wrote:
> >
> > 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.)
Right...when I saw your first response I started digging around one
of the standards and saw references to old and new transition tables
for statement-level triggers. That would be handy if it could be
implemented without scalability problems.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Ioseph Kim | 2005-01-28 00:19:43 | BUG #1444: ::int2 parser bug |
Previous Message | Alvaro Herrera | 2005-01-27 23:11:50 | Re: plpython triggers TD["new"] = None |