Re: History-based (or logged) database.

From: elein <elein(at)varlena(dot)com>
To: Chris Travers <chris(at)travelamericas(dot)com>
Cc: elein <elein(at)varlena(dot)com>, alvarezp(at)alvarezp(dot)ods(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: History-based (or logged) database.
Date: 2004-01-12 18:01:49
Message-ID: 20040112100149.J12147@cookie.varlena.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jbi130 2004-01-12 18:05:49 Connecting using an existing socket (libpq).
Previous Message D. Dante Lorenso 2004-01-12 18:01:06 Re: Drawbacks of using BYTEA for PK?