Re: Tantalizing reference to passing data from NEW variable - Mailing list pgsql-interfaces

From Joe Conway
Subject Re: Tantalizing reference to passing data from NEW variable
Date
Msg-id 408D4143.7040600@joeconway.com
Whole thread Raw
In response to Tantalizing reference to passing data from NEW variable in a trigger function...  (Rich Cullingford <rculling@sysd.com>)
Responses Re: Tantalizing reference to passing data from NEW variable  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Rich Cullingford wrote:
> This question seems to have been asked a number of times on this list, 
> recently (including by me) without being answered: how to pass the row 
> data stored in the NEW variable from a trigger function into a 
> sub-function. None of the obvious syntaxes work, including one by a 
> respondent in this list that suggested assigning NEW to a record 
> variable, and then passing *that*. After searching up and down the 
> archives, I see the following tantalizing snippet (from 6/2003) in the 
> context of a rule:

The standard answer to this has been to use PL/Tcl for your trigger
function instead of PL/pgSQL. I imagine PL/Python would work also, but
I'm not sure.

(FWIW, PL/R would work too, but I doubt you would want to install R just
to have this capability.)

I looked a bit at making this work in PL/pgSQL at some point -- IIRC the
issues to be solved were non-trivial.

Joe



pgsql-interfaces by date:

Previous
From: Bistey Csaba
Date:
Subject: BLIBPQ.LIB, BLIBPQDLL.LIB or LIBPQ 7.4 problem
Next
From: Kevin Cowley
Date:
Subject: Application compile file using Embeded SQL in Postgres4.7.2