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

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jozef Behran <jozef(dot)behran(at)krs(dot)sk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2089: Documentation bug: Triggers in plpythonu
Date: 2005-12-03 21:23:07
Message-ID: 20051203212307.GD32459@surnet.cl (view raw or flat)
Thread:
Lists: pgsql-bugs
Jozef Behran wrote:

> 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:

http://www.postgresql.org/docs/8.1/static/plpython-trigger.html

If this is not what you meant, please explain.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-bugs by date

Next:From: Dirk PirschelDate: 2005-12-03 21:24:35
Subject: Re: BUG #2092: No answer to bug reports 1975 and 2055
Previous:From: Bruno Wolff IIIDate: 2005-12-03 20:32:41
Subject: Re: BUG #2088: logfiles only readable by instance owner

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