Re: BUG #2089: Documentation bug: Triggers in plpythonu - Mailing list pgsql-bugs

From Jozef Behran
Subject Re: BUG #2089: Documentation bug: Triggers in plpythonu
Date
Msg-id 200512070942.35423.jozef.behran@krs.sk
Whole thread Raw
In response to Re: BUG #2089: Documentation bug: Triggers in plpythonu  (Alvaro Herrera <alvherre@commandprompt.com>)
List 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.

pgsql-bugs by date:

Previous
From: "Evan Carroll"
Date:
Subject: BUG #2097: Union bug.
Next
From: Tom Lane
Date:
Subject: Re: BUG #2097: Union bug.