Re: PL/pgSQL triggers with parameters don't work - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: PL/pgSQL triggers with parameters don't work
Date
Msg-id Pine.BSF.4.21.0107111059090.99439-100000@megazone23.bigpanda.com
Whole thread Raw
In response to PL/pgSQL triggers with parameters don't work  (pgsql-bugs@postgresql.org)
List pgsql-bugs
On Wed, 11 Jul 2001 pgsql-bugs@postgresql.org wrote:

> José María Fernández González (jmfernandez@cnb.uam.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.

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: ecpg: INITALLY DEFERRED translated into intially deferrable
Next
From: Tom Lane
Date:
Subject: Re: ERROR: deferredTriggerGetPreviousEvent: event for tuple (0,9) not found