From: | Felipe Schnack <felipes(at)ritterdosreis(dot)br> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Auditing idea |
Date: | 2003-08-07 22:30:50 |
Message-ID: | 20030807193050.730cd162.felipes@ritterdosreis.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey all! I had an idea to implement a very simple (IMHO) auditing mechanism for an application I'm developing, and thought some people here could give some hints, opinions, etc about it.
I was thinking about implementing update and delete triggers for all my tables that I want to be audited, and these triggers would create automatically the auditing message for me. Basically, the update triggers would store the row values in the OLD and NEW rows, and the delete trigger would store the values in the OLD row.
What you guys think of this idea? To me seems simple and good enough.
/~\ The ASCII Felipe Schnack (felipes(at)ritterdosreis(dot)br)
\ / Ribbon Campaign Analista de Sistemas
X Against HTML Cel.: 51-91287530
/ \ Email! Linux Counter #281893
Centro Universitário Ritter dos Reis
http://www.ritterdosreis.br
ritter(at)ritterdosreis(dot)br
Fone: 51-32303341
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Webster | 2003-08-07 23:44:05 | postmaster(s) have high load average |
Previous Message | Tom Lane | 2003-08-07 22:25:44 | Re: compile error of 7.4 beta1 on AIX 4.3.3 |