Content-Type: text/plain;
  charset="iso-8859-1"
From: Richard Huxton <dev@archonet.com>
Organization: Archonet Ltd
To: pgsql-sql@postgresql.org
Subject: Re: General trigger function
Date: Thu, 13 Jun 2002 09:50:45 +0100
User-Agent: KMail/1.4.1
References: <003401c211e5$9a5f1220$3d04a837@PXXXX>
	<3D07AFC5.8F5413BF@Yahoo.com>
In-Reply-To: <3D07AFC5.8F5413BF@Yahoo.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200206130950.45528.dev@archonet.com>

On Wednesday 12 Jun 2002 9:32 pm, Jan Wieck wrote:
> GRIMOIS Eric wrote:
> > Hi all
> >
> > I read in the doc than a same function can be used for several triggers.
> > I tried to create a function who updates a field with a timestamp and
> > another field with the user name. This function is fired by triggers in
> > several tables.
> > It only works if updated fields have same names in all tables. I failed
> > to create a function where fields names are parameters of the function.
>
>     You could do that with the EXECUTE functionality. But that
>     causes *every* execution of these statemets not beeing
>     cacheable, so it'll have an impact on performance.

Or look in the cookbook linked from techdocs.postgresql.org - there's an=20
example in there of a "trigger maker" which builds last-changed tracking=20
triggers and functions. You do something like:

select lastchg_addto('TABLE-NAME','TIMESTAMP-COLUMN-NAME')

And it creates the relevant function and trigger code then EXECUTEs it.=20
Shouldn't take much to alter it for your purposes

- Richard Huxton=20