Advice for generalizing trigger functions - Mailing list pgsql-sql

From Richard Broersma Jr
Subject Advice for generalizing trigger functions
Date
Msg-id 781842.52422.qm@web31813.mail.mud.yahoo.com
Whole thread Raw
Responses Re: Advice for generalizing trigger functions
Re: Advice for generalizing trigger functions
Re: Advice for generalizing trigger functions
List pgsql-sql
I've created quite a few functions that log modifications to various history tables. (the history table has the same
nameas the base table but is prefixed by the 'History.' schema.) The only difference between functions I can find is
thetable name.
 

Is there any way to generalize these myriad of functions into one?


Below is a sample of a typical logging trigger function.

Regards,
Richard Broersma Jr.


CREATE OR REPLACE FUNCTION "project"."log_managers_ops"()
RETURNS trigger AS
$BODY$
BEGIN

    IF TG_OP IN ( 'UPDATE', 'DELETE' ) THEN             UPDATE History.Managers AS M            SET endts = now()
  WHERE M.manager_id = OLD.manager_id            AND now() BETWEEN M.startts AND M.endts;                end IF;
   IF TG_OP IN ( 'UPDATE', 'INSERT' ) THEN        INSERT INTO History.Managers         VALUES ( now()::timestamptz,
'INFINITY'::timestamptz,NEW.*);
 
         RETURN NEW;             END IF;
    RETURN OLD;

END;
$BODY$
LANGUAGE 'plpgsql' VOLATILE SECURITY DEFINER;



pgsql-sql by date:

Previous
From: Rick Innis
Date:
Subject: Re: Misnamed field in subquery does not cause error when field name exists in parent query
Next
From: chester c young
Date:
Subject: Re: Advice for generalizing trigger functions