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

Re: PL/pgSQL triggers with parameters don't work

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: jmfernandez(at)cnb(dot)uam(dot)es, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PL/pgSQL triggers with parameters don't work
Date: 2001-07-11 18:03:01
Message-ID: Pine.BSF.4.21.0107111059090.99439-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, 11 Jul 2001 pgsql-bugs(at)postgresql(dot)org wrote:

> Jos Mara Fernndez Gonzlez (jmfernandez(at)cnb(dot)uam(dot)es) reports a bug
> with a severity of 2 
> The lower the number the more severe it is.
> 
> Short Description
> PL/pgSQL triggers with parameters don't work
> 
> Long Description
> 	The report is for PostgreSQL 7.1.2. When you create a trigger
> which calls a function with parameters, the system links against the
> function with the same name and no parameter, and if it doesn't exist
> it tells "function doesn't exist". Tests have been made with
> PL/pgSQL-encoded functions.

Trigger functions take their arguments in a different fashion.
They should be defined as taking no regular arguments and returning
opaque and it's something like TG_ARGS in plpgsql that the create
trigger time arguments are passed in.  I believe this is described in 
the documentation.



In response to

pgsql-bugs by date

Next:From: Kristis MakrisDate: 2001-07-11 18:13:41
Subject: Re: [BUGS] ERROR: deferredTriggerGetPreviousEvent: event for tuple(0,9) not found
Previous:From: Kannan The BarbarianDate: 2001-07-11 17:57:55
Subject: Upgrade to 7.1.2 problem

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