Serializability in object-oriented database systems
- 4 December 2002
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 112-120
- https://doi.org/10.1109/icde.1990.113460
Abstract
In an object-oriented database the objects are encapsulated, that is, objects are only accessible by methods defined in the database system. The definition of object-oriented serializability takes advantage of the semantics and of the nesting of the methods. Therefore, a lower rate of conflicting accesses than with the conventional definition of serializability is achieved. Transactions of an object-oriented database are defined as open-nested transactions. Depending on the semantics of operations, actions can be serialized independently of the calling transactions. The techniques already used in multilayer transaction systems are extended to object-oriented systems. Object-oriented serializability includes multilayer serializability but allows a nonlayered, more general structure of the database system.Keywords
This publication has 12 references indexed in Scilit:
- Coupling knowledge based systems with large data storesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2003
- A model for concurrency in nested transactions systemsJournal of the ACM, 1989
- Handling hot spot data in DB-sharing systemsInformation Systems, 1988
- Concurrent search structure algorithmsACM Transactions on Database Systems, 1988
- Vodak kernel data modelPublished by Springer Nature ,1988
- The Escrow transactional methodACM Transactions on Database Systems, 1986
- Synchronizing shared abstract typesACM Transactions on Computer Systems, 1984
- Locking Primitives in a Database SystemJournal of the ACM, 1983
- Concurrency on high-traffic data elementsPublished by Association for Computing Machinery (ACM) ,1982
- Ubiquitous B-TreeACM Computing Surveys, 1979