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: BUG #2089: Documentation bug: Triggers in plpythonu
Date: 2005-12-02 01:23:53
Message-ID: 20051202012353.E8B6BF0B6A@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2089
Logged by: Jozef Behran
Email address: jozef(dot)behran(at)krs(dot)sk
PostgreSQL version: 8.1.0
Operating system: Short answer: Mandrake 10.2. Long answer: Linux sarkan
2.6.11-6mdk #1 Tue Mar 22 16:04:32 CET 2005 i686 AMD Athlon(tm) Processor
unknown GNU/Linux
Description: Documentation bug: Triggers in plpythonu
Details:

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".

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2005-12-02 04:01:01 Re: [BUGS] BUG #2056: to_char no long takes time as input?
Previous Message Dick Snippe 2005-12-01 23:33:50 BUG #2088: logfiles only readable by instance owner