RE: using NEW in a trigger calling a function in plpgsq l... - Mailing list pgsql-general

From Creager, Robert S
Subject RE: using NEW in a trigger calling a function in plpgsq l...
Date
Msg-id 10FE17AD5F7ED31188CE002048406DE8514D1F@lsv-msg06.stortek.com
Whole thread Raw
Responses RE: using NEW in a trigger calling a function in plpgsq l...  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-general
What I'm attempting to do is set up a trigger function which calls another
function with the NEW/OLD as parameters to the other functions...  I'm a
software engineer, so I love to make functions :-)  If I call another
function, NEW/OLD is still 'scoped' within the other function?  The problem
is I'm a software engineer (wait, I mentioned that already), so my view of
the world is different...

Thanks,
Rob

> -----Original Message-----
>
> Trigger functions take no arguments and return opaque.
> Inside the plpgsql
> trigger you should automatically get NEW as the appropriate row, you
> shouldn't need to pass it in (you can use NEW in the body of the
> functions).
>

pgsql-general by date:

Previous
From: Gunnar R|nning
Date:
Subject: Problem migrating dump to latest CVS snapshot.
Next
From: "Vilson farias"
Date:
Subject: time representation bug