Hello all,
On Thu, 19 Apr 2007 09:27:33 -0400
Kenneth Downs <[EMAIL PROTECTED]> wrote:
> 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.
In tablelog (http://pgfound
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
applica
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
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
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?
Old - you already have the new version in the ma
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
applica
