Re: History-based (or logged) database. - Mailing list pgsql-general

From elein
Subject Re: History-based (or logged) database.
Date
Msg-id 20040112100149.J12147@cookie.varlena.com
Whole thread Raw
In response to Re: History-based (or logged) database.  ("Chris Travers" <chris@travelamericas.com>)
List pgsql-general
Yes, I did.  For just the simple updating, (not the
logging you are doing) NEW is what you want.  But OLD is proper
for archiving/logging.

--elein

On Mon, Jan 12, 2004 at 08:22:27PM +0700, Chris Travers wrote:
> Hi Elein;
>
> Nope, OLD is correct.  I track the OLD values and then use the view to
> combine those with the current ones.  This allows the OLAP portions of the
> code to hit against *all* the data, while archiving old, outdated
> information in the archive table.  It also allows deleted tuples to be
> tracked with the same trigger since a deleted row doesn't exactly have a NEW
> tuple :-) Maybe you misunderstand what I am trying to do?
>
> Best WIshes,
> Chris Travers

pgsql-general by date:

Previous
From: "D. Dante Lorenso"
Date:
Subject: Re: Drawbacks of using BYTEA for PK?
Next
From: "scott.marlowe"
Date:
Subject: Re: Case sensitivity