From: | Mark Gibson <gibsonm(at)cromwell(dot)co(dot)uk> |
---|---|
To: | David B <postgresql(at)thegatelys(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Elegant way to monitor for changes in a trigger and migrate |
Date: | 2004-02-11 08:39:24 |
Message-ID: | 4029EA3C.5000509@cromwell.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
David B wrote:
>Folks,
>
>Perhaps you can help....hell I'm sure you can!
>I want to monitor for changes in a table and migrate the OLD. record to
>audit table.
>
>Is there an elegant or generic way to do this so I can use across multiple
>tables with little change.
>
>
You can use a rule to do this:
CREATE RULE cust_audit AS ON UPDATE OR DELETE TO cust DO
INSERT INTO cust_hist SELECT OLD.*;
cust_hist should be identical to cust without a primary key or any
constraints/foreign keys etc.
I'm currently working on an auditing system at present, and will be
releasing it
soon if anyone is interested. It needs some cleaning up first, when I
have time.
--
Mark Gibson <gibsonm |AT| cromwell |DOT| co |DOT| uk>
Web Developer & Database Admin
Cromwell Tools Ltd.
Leicester, England.
From | Date | Subject | |
---|---|---|---|
Next Message | beyaNet Consultancy | 2004-02-11 13:05:04 | bytea or blobs? |
Previous Message | David B | 2004-02-11 01:18:46 | Elegant way to monitor for changes in a trigger and migrate record to history table |