2018
DOI: 10.1007/s11280-018-0552-7
|View full text |Cite
|
Sign up to set email alerts
|

Efficient time-interval data extraction in MVCC-based RDBMS

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 15 publications
0
2
0
Order By: Relevance
“…The newly generated record always maintain a link to its previous version (if any). According to the principle of MVCC, select/update/delete queries always locate the latest version of the record, and follow its link recursively to find a proper version based on the snapshot isolation mechanism [7,26,23]. Apparently, as compared to the temporal counterpart, in a non-temporal relation, the latest version of a record corresponds to the current record, and its previous versions correspond to historical records.…”
Section: Current Data Storagementioning
confidence: 99%
See 1 more Smart Citation
“…The newly generated record always maintain a link to its previous version (if any). According to the principle of MVCC, select/update/delete queries always locate the latest version of the record, and follow its link recursively to find a proper version based on the snapshot isolation mechanism [7,26,23]. Apparently, as compared to the temporal counterpart, in a non-temporal relation, the latest version of a record corresponds to the current record, and its previous versions correspond to historical records.…”
Section: Current Data Storagementioning
confidence: 99%
“…Consider the majority of conventional DBMSs, including Oracle, SQL Server, MySQL, are MVCC-based. Theoretically, for a given record r, the start time (or end time) in its transaction time should be set to the commit time of the transaction that creates (or updates/deletes) r based on the snapshot isolation theorem [7,23,26]. Nevertheless, most of the existing temporal implementations just pick up the time when transaction starts to execute, or the time of the operation that inserts/updates/deletes the record (note that conventional DBMSs do not maintain the commit time of the transaction with each record by taking into consideration the performance of the whole system) just because SQL:2011 does not enforce to use the commit time [21].…”
Section: Introductionmentioning
confidence: 99%