| From: | Bernhard Weisshuhn <bkw(at)weisshuhn(dot)de> |
|---|---|
| To: | Rodrigo Sakai <rodrigo(dot)sakai(at)poli(dot)usp(dot)br> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Temporal Databases |
| Date: | 2006-02-23 21:52:13 |
| Message-ID: | 20060223215213.GA10385@weisshuhn.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 23, 2006 at 03:34:36PM -0300, Rodrigo Sakai <rodrigo(dot)sakai(at)poli(dot)usp(dot)br> wrote:
> I'm focus on temporal databases (not temporary), and I want to know if anyone here is studying this tecnologies too. So, we can exchange knowlegment. Specifically, anyone who is trying to implement on postgresql the aspect of time (temporal).
> These researches are lead by Richard Snodgrass. So, anyone who have something to share, please contact me!
Not sure if I understand the problem correctly, but the contrib/spi/timetravel
module does something which I think may be what you are talking about.
http://developer.postgresql.org/cvsweb.cgi/~checkout~/pgsql/contrib/spi/README.timetravel
The docs are a bit cryptic but you should be able to grasp if it suits
your needs. Basically you can go back to any point in tabe for a
timetravel table and make date based comparisons.
Hope this helps, forgive my ignorance if if doesn't.
bkw
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-23 21:52:36 | Re: How I changed the encoding of template1 after the fact |
| Previous Message | Tom Lane | 2006-02-23 21:43:27 | Re: Limitations : Number of ... |