1995
DOI: 10.1007/bfb0049157
|View full text |Cite
|
Sign up to set email alerts
|

Concurrency control in nested transactions with enhanced lock modes for KBMSs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

1996
1996
2005
2005

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(2 citation statements)
references
References 8 publications
0
2
0
Order By: Relevance
“…The model of nested transactions we assume makes maximum parallelism in a transaction hierarchy possible, allowing for parent-child as well as sibling parallelism (as is the case in Camelot [6,7], Clouds [8,9], Eden [10,11], LOCUS [12,13], KRISYS [4,14] etc.) 4 .…”
Section: Lock Managermentioning
confidence: 99%
See 1 more Smart Citation
“…The model of nested transactions we assume makes maximum parallelism in a transaction hierarchy possible, allowing for parent-child as well as sibling parallelism (as is the case in Camelot [6,7], Clouds [8,9], Eden [10,11], LOCUS [12,13], KRISYS [4,14] etc.) 4 .…”
Section: Lock Managermentioning
confidence: 99%
“…Nested transactions have been implemented in many systems (Argus [21][22][23], Camelot [6,7], Clouds [8,9], Eden [10,11], LOCUS [12,13], KRISYS [4,14], PRIMA [19] etc.). Unfortunately, very little has been published on the strategies employed by those systems for assigning identi"ers (exceptions are [7,20]).…”
Section: Related Workmentioning
confidence: 99%