From: | David <wizzardx(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Database design: Temporal databases |
Date: | 2008-06-18 12:05:34 |
Message-ID: | 18c1e6480806180505w60560eefm8dad5800975f418e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi list.
Some background information on the subject:
http://en.wikipedia.org/wiki/Temporal_database
I haven't used them before, but I like the idea of never
deleting/updating records so you have a complete history (a bit like
source code version control).
How well do temporal databases work? Do RDBMS (ie Postgresql) need
add-ons to make it effective, or can you just add extra temporal
columns to all your tables and add them to your app queries? Does this
increase app complexity and increase server load a lot?
Are there Python libraries which simplify this? (eg: add-ons for
Elixir or SQLAlchemy).
Or should apps all implement their own 'temporal data access' module,
which transparently uses the current date & time until queried for
historical data?
David.
From | Date | Subject | |
---|---|---|---|
Next Message | David | 2008-06-18 12:07:26 | Database design: Data synchronization |
Previous Message | David | 2008-06-18 12:04:14 | Database design: Backwards-compatible field addition |