Re: challenging constraint situation - how do I make it real in SQL?

From: "John D(dot) Burger" <john(at)mitre(dot)org>
To: "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: challenging constraint situation - how do I make it real in SQL?
Date: 2006-05-24 13:30:25
Message-ID: 15d22de683381aada63e265d4353b313@mitre.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I have a business rule which gives me rahter big challenges to "melt
> in SQL":
>
> At one "point in time" only one version may be active.

I have no specific solution, but I highly recommend Richard Snodgrass's
book, Developing Time-Oriented Database Applications in SQL, which
discusses this kind of situation, and many other similar ones. It's
out of print, but available from his homepage as a PDF:

http://www.cs.arizona.edu/~rts/

- John D. Burger
MITRE

In response to

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2006-05-24 13:36:28 Re: column order
Previous Message Sim Zacks 2006-05-24 13:27:25 Re: background triggers?