Re: Auditing a database - Mailing list pgsql-general

From Kenneth Downs
Subject Re: Auditing a database
Date
Msg-id 46276E45.2080308@secdat.com
Whole thread Raw
In response to Auditing a database  (Germán Hüttemann Arza <ghuttemann@gmail.com>)
Responses Re: Auditing a database  (Andreas 'ads' Scherbaum <adsmail@wars-nicht.de>)
List pgsql-general
Ask the question: can I make sure I always have a complete trail?  If
you insert the old row, you will always have the old values and the
table itself holds the new values.

Germán Hüttemann Arza wrote:
> Hi,
>
> I am developing a web application for auditing tables from a postgresql
> database.
>
> My question is: when an update occurrs in the base table, should I insert in
> the auditing table the new record or the old one?
>
> I was first inserting the new one but a job partner, who are testing the
> application suggested that probably would be better to insert the old record
> because it is simpler to follow the trace of updates.
>
> What you suggest?
>
> Regards,
>
>


--
Kenneth Downs
Secure Data Software, Inc.
www.secdat.com    www.andromeda-project.org
631-379-7200   Fax: 631-689-0527


pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Auditing a database
Next
From: "Peter Neu"
Date:
Subject: Need help with db script, and daily routines