Re: Auditing a database

From: Kenneth Downs <ken(at)secdat(dot)com>
To: Germán Hüttemann Arza <ghuttemann(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Auditing a database
Date: 2007-04-19 13:27:33
Message-ID: 46276E45.2080308@secdat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Neu 2007-04-19 13:28:18 Need help with db script, and daily routines
Previous Message Richard Huxton 2007-04-19 13:25:32 Re: Auditing a database