Comparison of access methods for time-evolving data
ACM Computing Surveys (CSUR)
Transaction Timestamping in (Temporal) Databases
Proceedings of the 27th International Conference on Very Large Data Bases
Temporally Faithful Execution of Business Transactions
CAiSE '00 Proceedings of the 12th International Conference on Advanced Information Systems Engineering
Effective timestamping in databases
The VLDB Journal — The International Journal on Very Large Data Bases
Tamper detection in audit logs
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
Nested bitemporal relational algebra
ISCIS'06 Proceedings of the 21st international conference on Computer and Information Sciences
| Hi-index | 0.00 |
Many applications need transaction-consistent pictures of past states of the database. These applications use the commit time of the transaction to timestamp the data. When a transaction is distributed, the cohorts must vote on a commit time and the coordinator must choose a commit time based on the votes of the cohorts. This implies that timestamps are applied after commit.Until the timestamps are on all the records, one must keep a table of all the committed transaction identifiers and their commit times. The main problem solved is that of determining when all timestamps corresponding to a given transaction have been placed in the records so that a committed transaction entry can be erased from the table. This information must be stable. Logging and recovery details are included.