Expiration Times for Data Management

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

2 Citations (Scopus)

Abstract

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
Pages36-
ISBN (Print)0769525709
DOIs
Publication statusPublished - 2006
EventInternational Conference on Data Engineering - Atlanta, GA, United States
Duration: 3 Apr 20067 Apr 2006
Conference number: 22

Conference

ConferenceInternational Conference on Data Engineering
Number22
CountryUnited States
CityAtlanta, GA
Period03/04/200607/04/2006

Fingerprint

Information management
World Wide Web
Mobile devices
Web services
Algebra
Data structures
Wireless networks

Cite this

Schmidt, A., Jensen, C. S., & Saltenis, S. (2006). Expiration Times for Data Management. In Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06 (pp. 36-). Electrical Engineering/Electronics, Computer, Communications and Information Technology Association. https://doi.org/10.1109/ICDE.2006.66
Schmidt, Albrecht ; Jensen, Christian Søndergaard ; Saltenis, Simonas. / Expiration Times for Data Management. Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06. Electrical Engineering/Electronics, Computer, Communications and Information Technology Association, 2006. pp. 36-
@inproceedings{4c1971b0a9f111dbb942000ea68e967b,
title = "Expiration Times for Data Management",
abstract = "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.",
author = "Albrecht Schmidt and Jensen, {Christian S{\o}ndergaard} and Simonas Saltenis",
year = "2006",
doi = "10.1109/ICDE.2006.66",
language = "English",
isbn = "0769525709",
pages = "36--",
booktitle = "Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06",
publisher = "Electrical Engineering/Electronics, Computer, Communications and Information Technology Association",

}

Schmidt, A, Jensen, CS & Saltenis, S 2006, Expiration Times for Data Management. in Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06. Electrical Engineering/Electronics, Computer, Communications and Information Technology Association, pp. 36-, International Conference on Data Engineering, Atlanta, GA, United States, 03/04/2006. https://doi.org/10.1109/ICDE.2006.66

Expiration Times for Data Management. / Schmidt, Albrecht; Jensen, Christian Søndergaard; Saltenis, Simonas.

Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06. Electrical Engineering/Electronics, Computer, Communications and Information Technology Association, 2006. p. 36-.

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

TY - GEN

T1 - Expiration Times for Data Management

AU - Schmidt, Albrecht

AU - Jensen, Christian Søndergaard

AU - Saltenis, Simonas

PY - 2006

Y1 - 2006

N2 - 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.

AB - 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.

U2 - 10.1109/ICDE.2006.66

DO - 10.1109/ICDE.2006.66

M3 - Article in proceeding

SN - 0769525709

SP - 36-

BT - Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06

PB - Electrical Engineering/Electronics, Computer, Communications and Information Technology Association

ER -

Schmidt A, Jensen CS, Saltenis S. Expiration Times for Data Management. In Proceedings of the 22nd International Conference on Data Engineering, 2006. ICDE '06. Electrical Engineering/Electronics, Computer, Communications and Information Technology Association. 2006. p. 36- https://doi.org/10.1109/ICDE.2006.66