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

Re: BUG #2089: Documentation bug: Triggers in plpythonu

From: Jozef Behran <jozef(dot)behran(at)krs(dot)sk>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2089: Documentation bug: Triggers in plpythonu
Date: 2005-12-07 08:42:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
> > A trigger in plpythonu cannot use the `args' list to obtain the
> > arguments and does not return the row to be written into the
> > database. Instead the arguments are placed into a global
> > dictionary called "TD". The row is in TD["new"] as a dictionary
> > keyed by the names of the fields (the values are the values of
> > the field). The trigger is supposed to return "SKIP" (or None?)
> > if it wants the operation to be skipped or modify the TD["new"]
> > to the actual content to be written into the database and then
> > return "MODIFY".
> I don't see how is this a bug.  It's perfectly documented in the
> "Trigger functions" section, here:

The problem was that I mistakenly read manual for the 8.0 version,
in which this is not documented (or at least no link is created from 
the "trigger functions". There is no such bug in 8.1 manual and since 
I use version 8.1.0 now, this does not matter.

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-12-07 15:00:31
Subject: Re: BUG #2097: Union bug.
Previous:From: Evan CarrollDate: 2005-12-07 06:03:19
Subject: BUG #2097: Union bug.

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