| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Rodrigo Sakai <rodrigo(dot)sakai(at)poli(dot)usp(dot)br> |
| Cc: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Michael Glaesemann <grzm(at)myrealbox(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Temporal Databases |
| Date: | 2006-03-09 03:51:05 |
| Message-ID: | 20060309035105.GA12415@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Mar 08, 2006 at 12:56:38 -0300,
Rodrigo Sakai <rodrigo(dot)sakai(at)poli(dot)usp(dot)br> wrote:
> Ok, but actually I'm not concerned about logging old values. I'm concerned
> about checking temporal constraints. Entity Integrity (PK) and Referential
> Integrity (FK).
Did you see the reference to 'Developing Time-Oriented Database Applications
in SQL' (http://www.cs.arizona.edu/people/rts/tdbbook.pdf) in a recent thread?
That should give you some trigger code you can use to do this kind of thing.
It isn't postgres specific, but shouldn't need too much work.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noel Faux | 2006-03-09 04:57:46 | Re: Data corruption zero a file - help!! |
| Previous Message | Michael Fuhr | 2006-03-09 03:26:29 | Re: Data corruption zero a file - help!! |