From: | Mike Rylander <mrylander(at)gmail(dot)com> |
---|---|
To: | Zlatko Matic <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> |
Cc: | Postgresql-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Audit trail ? |
Date: | 2005-05-29 16:21:17 |
Message-ID: | b918cf3d0505290921d2eceef@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/29/05, Zlatko Matic <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> wrote:
> Hello.
>
> I must have audit trail of all insert/update/delete on several table. I have
> several questions regarding that:
>
> 1. Is it better to have one audit trail table that collects
> insert/update/delete of all audited tables, or it is better to have separate
> audit trail table for every audited table ?
> 2. To use triggers or rules ? Example for both ?
> 3. Could someone give me an example of a successfull audit trail solution ?
>
> I'm running on lack of time, so any help would be precious...
We use the "audit table per real table" approach. The SQL script to
create the audit trail functions and triggers is attached. There are
three example audit trail table creation calls right before the
COMMIT.
Hope that helps!
--
Mike Rylander
mrylander(at)gmail(dot)com
GPLS -- PINES Development
Database Developer
http://open-ils.org
Attachment | Content-Type | Size |
---|---|---|
900.audit-tables.sql | application/octet-stream | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Mohan, Ross | 2005-05-29 16:22:59 | Re: Fast request for version checking.... |
Previous Message | Bob | 2005-05-29 16:09:59 | Re: Audit trail ? |