Expiration Times for Data Management

Research output: Contribution to book/anthology/report/conference proceedingArticle in proceedingResearchpeer-review

2 Citations (Scopus)


This paper describes an approach to incorporating the notion of expiration time into data management based on the relational model. Expiration times indicate when tuples cease to be current in a database. The paper presents a formal data model and a query algebra that handle expiration times transparently and declaratively. In particular, expiration times are exposed to users only on insertion and update, and when triggers fire due to the expiration of a tuple; for queries, they are handled behind the scenes and do not concern the user. Notably, tuples are removed automatically from (materialised) query results as they expire in the (base) relations. For application developers, the benefits of using expiration times are (1) leaner application code, (2) lower transaction volume, (3) smaller databases, and, (4) higher consistency for replicated data with lower overhead. Expiration times turn out to be especially useful in open architectures and loosely-coupled systems, which abound on the World Wide Web as well as in mobile networks, be it as Web Services or as ad hoc and intermittent networks of mobile devices.
Original languageEnglish
Title of host publicationProceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06
Number of pages11
PublisherElectrical Engineering/Electronics, Computer, Communications and Information Technology Association
Publication date2006
ISBN (Print)0769525709
Publication statusPublished - 2006
EventInternational Conference on Data Engineering - Atlanta, GA, United States
Duration: 3 Apr 20067 Apr 2006
Conference number: 22


ConferenceInternational Conference on Data Engineering
Country/TerritoryUnited States
CityAtlanta, GA


Dive into the research topics of 'Expiration Times for Data Management'. Together they form a unique fingerprint.

Cite this