Re: History-based (or logged) database.

From: "Chris Travers" <chris(at)travelamericas(dot)com>
To: "elein" <elein(at)varlena(dot)com>
Cc: <alvarezp(at)alvarezp(dot)ods(dot)org>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: History-based (or logged) database.
Date: 2004-01-12 13:22:27
Message-ID: 00af01c3d910$1b3220c0$71285e3d@winxp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Garamond 2004-01-12 13:42:36 Re: Drawbacks of using BYTEA for PK?
Previous Message Christopher Browne 2004-01-12 12:57:26 Re: what we need to use postgresql in the enterprise