The Community for Technology Leaders
Database Engineering and Applications Symposium, International (2005)
Montreal, Canada
July 25, 2005 to July 27, 2005
ISSN: 1098-8068
ISBN: 0-7695-2404-4
pp: 357-368
Christian S. Jensen , Aalborg University
David Lomet , Microsoft Research
Richard T. Snodgrass , University of Arizona
ABSTRACT
Our goal is to support transaction-time functionality that enables the coexistence of ordinary, non-temporal tables with transaction-time tables. In such a system, each transaction updating a transaction-time or snapshot table must include a timestamp for its updated data that correctly reflects the serialization order of the transactions, including transactions on ordinary tables. A serious issue is coping with SQL CURRENT_TIME functions, which should return a time consistent with a transaction?s timestamp and serialization order. Prior timestamping techniques cannot support such functions with this desired semantics. We show how to compatibly extend conventional database functionality for transaction-time support by exploiting the database system lock manager and by utilizing a spectrum of optimizations.
INDEX TERMS
null
CITATION
Christian S. Jensen, David Lomet, Richard T. Snodgrass, "Using the Lock Manager to Choose Timestamps", Database Engineering and Applications Symposium, International, vol. 00, no. , pp. 357-368, 2005, doi:10.1109/IDEAS.2005.53
86 ms
(Ver )