From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Subject: | Re: FW: bitemporal functionality for PostgreSQL |
Date: | 2008-02-04 09:16:43 |
Message-ID: | 200802041016.43997.dfontaine@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Le dimanche 03 février 2008, Greg Smith a écrit :
> On Sun, 3 Feb 2008, Jeff Davis wrote:
> > I think what he means by "bitemporal" is what CJ Date, et al., refer to
> > as "fully temporal" (as opposed to semi-temporal), that is, dealing with
> > time intervals rather than time points.
>
> >> I would suggest a book called "Temporal Data and the Relational Model",
> >> by C. J. Date, Hugh Darwen and Nikos A Lorentzos to anyone who's
> >> interested in temporal issues.
>
> I think you need to be familiar with the work set down in both that one
> and the Snodgrass/Jensen "Developing Time-Oriented Database Applications
> in SQL" before you can even start do anything that's actually new in this
> area. Bitemporal tables show up early in that book (P44 of the PDF
> http://www.cs.arizona.edu/people/rts/tdbbook.pdf )
I found the following document quite useful to grasp the concepts involved, it
allowed me to decide whether I needed bitemporal feature or not (was not) :)
http://rueping.info/doc/Andreas Rüping -- 2D History.pdf
Hope this helps, regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-02-04 09:39:59 | Re: configurability of OOM killer |
Previous Message | Amit jain | 2008-02-04 08:56:31 | Merge condition in postgresql |