2010 Second International Conference on Advances in Databases, Knowledge, and Data Applications 2010
DOI: 10.1109/dbkda.2010.25
|View full text |Cite
|
Sign up to set email alerts
|

Implementing Optimistic Concurrency Control for Persistence Middleware Using Row Version Verification

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2021
2021
2021
2021

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(7 citation statements)
references
References 8 publications
0
7
0
Order By: Relevance
“…HTTP offers ETags [17] in response to allow caching of results, and ETags can be used for validating a step in a transaction. ETags are very similar to the RVV concept [27] or Multi-Version Concurrency Control (MVCC), successfully used in PostgreSQL [28], SQL server [29], Oracle etc. to provide optimistic execution.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…HTTP offers ETags [17] in response to allow caching of results, and ETags can be used for validating a step in a transaction. ETags are very similar to the RVV concept [27] or Multi-Version Concurrency Control (MVCC), successfully used in PostgreSQL [28], SQL server [29], Oracle etc. to provide optimistic execution.…”
Section: Related Workmentioning
confidence: 99%
“…The RVV protocol is a type of version control mechanism, which can be used for a form of optimistic concurrency control, alongside or in preference to other versioning measures such as MVCC. The model implementations of RVV in the Laiho/Laux paper [27] envisage a sequence generator to ensure uniqueness of RVV values, so that new values of this sequence are added as a special row-version column in base tables on each INSERT or UPDATE. Some Database Management Systems (DBMSs) include row versioning mechanisms that can be used for this.…”
Section: A Row-version Validationmentioning
confidence: 99%
See 1 more Smart Citation
“…With the dissemination of middleware OCC has been recommended by , [21], [22]) for transactional e-business and m-commerce applications but little concern have been spend on how this can be achieved using commercial SQL databases [7]. Heß [20] simply uses Hibernate's optimistic-lock="version" option but does not mention the risk of legacy applications not under control of Hibernate which could still lead to lost updates.…”
Section: Related Workmentioning
confidence: 99%
“…Heß [20] simply uses Hibernate's optimistic-lock="version" option but does not mention the risk of legacy applications not under control of Hibernate which could still lead to lost updates. Nock [6] uses a timestamp column with Java timestamp resolution ignoring the fact that contemporary database products can produce more than a hundred times the same timestamp [7]. Akbar-Husain [21] believes that demarking the method that checks the version with the required transaction attribute will be sufficient to avoid lost updates.…”
Section: Related Workmentioning
confidence: 99%