From: Michael Glaesemann <grzm@myrealbox.com>
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
Cc: Ken Winter <ken@sunward.org>
Cc: 'Richard Huxton' <dev@archonet.com>
Cc: 'PostgreSQL pg-sql list' <pgsql-sql@postgresql.org>
Subject: Re: Still struggling with history tables
Date: Wed, 18 Jan 2006 18:59:28 +0900
Message-ID: <AD84FC1A-4BF7-4A39-979B-675194CC1D65@myrealbox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0601181145380.14453-100000@matrix.gatewaynet.com>
References: <Pine.LNX.4.44.0601181145380.14453-100000@matrix.gatewaynet.com>
On Jan 18, 2006, at 19:23 , Achilleus Mantzios wrote:
> Generally it is very hard to distinguish between two kind of UPDATES:
>
> a) UPDATEs that mean real data updates and they should be recorded
> to the history system.
> b) UPDATEs that are just false data entry, and they should mean
> just plain correction UPDATES, with no recording.
>
> This distinguishability is very important, otherwise someone would
> define a way to store historic data of changes to the historic data
> themselves, and so on.
Just a quick note:
Sometimes the term "valid-time" is used to talk about the interval of
data validity, and tables that include valid-time intervals are
sometimes referred to as "state tables". If you're interested in
tracking when corrections are made, this is referred to as
"transaction-time". Correcting the is sometimes called a
"nonsequenced" update, because it's not correcting the sequence of
validity: it's just a correction.
For more information, you can check out "Developing Time-Oriented
Database Applications in SQL" by Richard Snodgrass (available as a
free PDF download from his website[1]), or, for more theoretical
information, "Temporal Data and the Relational Model" by CJ Date,
Hugh Darwen, and Nikos Lorentzos.[2]
Michael Glaesemann
grzm myrealbox com
[1](http://www.cs.arizona.edu/people/rts/tdbbook.pdf)
[2](http://www.amazon.com/gp/product/1558608559/)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: grzm@myrealbox.com, achill@matrix.gatewaynet.com, ken@sunward.org, dev@archonet.com
Subject: Re: Still struggling with history tables
In-Reply-To: <AD84FC1A-4BF7-4A39-979B-675194CC1D65@myrealbox.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox