Hello, Mike!
Your solution for audit trail is wonderfull! Easy and elegant !
It helped me a lot and I successfully implemented it, with small
modifications.
Thanky you very much!
----- Original Message -----
From: "Mike Rylander" <mrylander@xxxxxxxxx>
To: "Zlatko Matic" <zlatko.matic1@xxxxxxxxxxx>
Cc: "Postgresql-General" <pgsql-general@xxxxxxxxxxxxxx>
Sent: Sunday, May 29, 2005 6:21 PM
Subject: Re: Audit trail ?
On 5/29/05, Zlatko Matic <zlatko.matic1@xxxxxxxxxxx> 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@xxxxxxxxx
GPLS -- PINES Development
Database Developer
http://open-ils.org
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
