Thread

1. Auditing idea

   Felipe Schnack <felipes@ritterdosreis.br> — 2003-08-07T22:30:50Z

     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@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
   ritter@ritterdosreis.br
   Fone: 51-32303341
   
   

2. Re: Auditing idea

   Chris Hutchinson <chris@hutchinsonsoftware.com> — 2003-08-08T03:04:34Z

   Felipe,
   
   This article might be of interest. It implements exactly the functionality
   you describe:
   http://philip.greenspun.com/internet-application-workbook/examples-content-m
   anagement/audit-acs-doc
   
   Regards,
   Chris
   
   >  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.
   
   
   
   

3. Re: Auditing idea

   Mike Benoit <mikeb@netnation.com> — 2003-08-08T16:36:42Z

   You might want to take a look at this project:
   http://gborg.postgresql.org/project/tablelog/download/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 (felipes@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
   > ritter@ritterdosreis.br
   > Fone: 51-32303341
   > 
   > ---------------------------(end of broadcast)---------------------------
   > TIP 6: Have you searched our list archives?
   > 
   >                http://archives.postgresql.org
   -- 
   Best Regards,
    
   Mike Benoit
   
   
   
   

4. Re: Auditing idea

   scott.marlowe <scott.marlowe@ihs.com> — 2003-08-08T16:40:23Z

   I think it's the SPI package from Hans...
   
   On Fri, 8 Aug 2003, Mike Benoit wrote:
   
   > You might want to take a look at this project:
   > http://gborg.postgresql.org/project/tablelog/download/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 (felipes@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
   > > ritter@ritterdosreis.br
   > > Fone: 51-32303341
   > > 
   > > ---------------------------(end of broadcast)---------------------------
   > > TIP 6: Have you searched our list archives?
   > > 
   > >                http://archives.postgresql.org
   >