Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!chomicki
From: chomicki@cis.ksu.edu (Jan Chomicki)
Newsgroups: comp.databases
Subject: Applications of Temporal Integrity Constraints
Keywords: logical integrity
Message-ID: <1991May6.205114.4386@maverick.ksu.ksu.edu>
Date: 6 May 91 20:51:14 GMT
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University, Department of Computing and Information Sciences
Lines: 22
Nntp-Posting-Host: antares.cis.ksu.edu

I'm interested in finding out about possible applications of Temporal
Integrity Constraints in databases. The constraints can be very general
and refer to the entire database history, like "if an employee has been
fired in the past, he/she should never be rehired". 

How are such constraints usually implemented? Is there a need to
provide a declarative framework for their specification, using for
example Temporal Logic? Are Temporal Conditions in Rules, like "if the
price of the stock X has been declining, sell X", useful?

Any comments and references to papers describing real-life
applications where Temporal Integrity is important will be very much
appreciated. I'm familiar with the theoretical work on implementing
constraints formulated in Temporal Logic and I have developed one such
a method myself.

--
Jan Chomicki				Computing and Information Sciences
					234 Nichols Hall
Internet: chomicki@harris.cis.ksu.edu	Kansas State University
Phone: (913) 532-6350			Manhattan, KS 66506-2302