By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,303 Members | 1,239 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,303 IT Pros & Developers. It's quick & easy.

Auditing idea

P: n/a
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 (fe*****@ritterdosreis.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
ri****@ritterdosreis.br
Fone: 51-32303341

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 11 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
You might want to take a look at this project:
http://gborg.postgresql.org/project/...d/download.php

There is another project similar to that one on gborg as well, but I
don't recall the name at this time.

On Thu, 2003-08-07 at 15:30, Felipe Schnack wrote:
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 (fe*****@ritterdosreis.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
ri****@ritterdosreis.br
Fone: 51-32303341

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

--
Best Regards,

Mike Benoit

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 11 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.