Advertisement

Stamp locking method for multiversion composite objects

  • Wojciech Cellary
  • Waldemar Wieczerzycki
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 730)

Abstract

In this paper a new approach to locking multiversion composite objects is proposed, called the stamp locking approach. The main notion of this approach is a stamp lock defined as an extension of a classical lock in such a way that it contains the information about the position of locked nodes in the hierarchies concerned. The main advantage of this method is simple locking strategy following from the lack of intentional locks. To lock a hierarchy subtree it is sufficient to set one stamp lock only, whose node stamp identifies the subtree root. To determine stamp lock compatibility, it is sufficient to compare stamps that are particular identifiers of hierarchy nodes and subtrees. Advantages of the stamp locking method become particularly beneficial in the case of a database containing many versions of composite objects, whose composition structure is complex. This is a typical case of design databases where objects, being the artifacts of the design process, have usually many components available in many versions.

Keywords

Single Object Composite Object Database Version Object Version Composition Tree 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [1]
    Ahmed R., Navathe S.B., “Version Management of Composite Objects in CAD Databases“, Proc. ACM SIGMOD Conf., 1991.Google Scholar
  2. [2]
    Cart M., Ferrie J. “Integrating Concurrency Control into Object-Oriented Database System”, EDBT Proc, Venice, Italy, 1990.Google Scholar
  3. [3]
    Cellary W., Jomier G., “Consistency of Versions in Object-Oriented Databases”, Proc. 16 th VLDB Conf., Brisbane, Aug. 1990, pp. 432–441.Google Scholar
  4. [4]
    Chou H., Kim W., “A Unifying Framework for Version Control in CAD Environment”, 12 VLDB Conf., Kyoto, Aug. 1986.Google Scholar
  5. [5]
    Gray J. “Notes on Database Operating Systems”, Operating Systems: An Advanced Course, Springer-Verlag, 1978.Google Scholar
  6. [6]
    Hubel C, Kafer W., Sutter B., “Controlling Cooperation Through Design-Object Specification, a Database-oriented Approach“, Proc. of the European Design Automation Conf., Brussels, Belgium, 1992.Google Scholar
  7. [7]
    Kim W., Bertino E., Garza J.F “Composite Objects Revisited”, Proc. ACMSIGMOD Conf, 1989.Google Scholar
  8. [8]
    Zdonik S.B. “Version Management in an Object-Oriented Database”, Int. Works. on Advanced Programming Environments, Norway 1986, pp. 139–200.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Wojciech Cellary
    • 1
  • Waldemar Wieczerzycki
    • 1
  1. 1.Franco-Polish School of New Information and Communication TechnologiesPoznańPoland

Personalised recommendations