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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
