Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: challenging constraint situation - how do I make it real in SQL?
- From: "John D. 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: Wed, 24 May 2006 09:30:25 -0400
- Message-id: <15d22de683381aada63e265d4353b313(at)mitre(dot)org>
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
- References:
- challenging constraint situation - how do I make it real in SQL?
- From: Harald Armin Massa
- challenging constraint situation - how do I make it real in SQL?
- Prev by Date: Re: [SQL] (Ab)Using schemas and inheritance
- Next by Date: Re: column order
- Previous by thread: Re: Vector type (Re: challenging constraint situation -
- Next by thread: Clearing out old idle connections
- Indexes: