Multidimensional versioning for object-oriented databases

  • Edward Sciore
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 566)


Many database applications require the storage and manipulation of different versions of data objects. However, current database systems do not support versioning well. Each application area treats versions in its own way, and these ways are usually incompatible with each other. We show how this incompatibility can be resolved by separating the physical, conceptual, and logical levels of versioning. We develop a version specification language at the conceptual level, and a multidimensional specification language at the logical level. By encoding the logical versioning semantics of an application into orthogonal dimensions, we generalize the ideas of historical and temporal databases to arbitrary object-oriented databases. The result is a unified, application-independent treatment of versioning.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [Ban87]
    Banerjee, J. et al. “Data Model Issues for Object-Oriented Applications.” ACM Transactions on Office Information Systems 5, 1(Jan. 1987), pp. 3–26.Google Scholar
  2. [BaKi85]
    Batory, D. and Kim, W. “Modelling Concepts for VLSI CAD Objects.” ACM Transactions on Database Systems 10, 3 (Sept. 1985), pp. 322–346.Google Scholar
  3. [BeMa88]
    Beech, D. and Mahbod, B. “Generalized Version Control in an Object-Oriented Database.” Proc. IEEE Data Engineering Conference (Feb. 1988), pp. 14–22.Google Scholar
  4. [BeEs86]
    Belkhatir, N. and Estublier, J. “Experience with a Data Base of Programs.” Proc. ACM SIGSOFT-SIGPLAN Symposium on Practical Software Development Environments (Dec. 1986), pp. 84–91.Google Scholar
  5. [Bil89]
    Biliris, Alexandros, “Database Support for Evolving Design Objects.” Proc. ACM-IEEE Design Automation Conference (June 1989).Google Scholar
  6. [Bil90]
    Biliris, Alexandras, “Modelling Design Object Relationships in PEGASUS.” Proc. IEEE Data Engineering Conf. (Feb. 1990), pp. 228–236.Google Scholar
  7. [CaDeVa88]
    Carey, M., DeWill, D., and Vandenberg, S. “A Data Model and Query Language for EXODUS.” Poc. ACM-SIGMOD Conf. (June 1988), pp. 413–423.Google Scholar
  8. [ChKi86]
    Chou, H.T. and Kim, W. “A Unifying Framework for Versions in a CAD Environment.” Proc. VLDB Conf. (Aug. 1986), pp. 336–344.Google Scholar
  9. [ClCr87]
    Clifford, J. and Croker, A. “The Historical Relation Data Model (HRDM) and Algebra based on Lifespans.” Proc. IEEE Data Engineering Conf. (Feb. 1987), pp. 528–537.Google Scholar
  10. [Coh88]
    Cohen, E. et al, “Version Management in Gypsy.” Proc. ACM SIGSOFTSIGPLAN Symposium on Practical Software Development Environments, (Nov. 1988), pp. 201–215.Google Scholar
  11. [DiLo88]
    Dittrich, K. and Lorie, R. “Version Support for Engineering Database Systems.” IEEE Transactions on Software Engineering 14, 4 (April 1988), pp. 429–437.Google Scholar
  12. [GaYe88]
    Gadia, S. and Yeung, C. “A Generalized Model for a Relational Temporal Database.” Proc. ACM SIGMOD Conference (June 1988), pp. 48–69.Google Scholar
  13. [HuKi88]
    Hudson, S. and King, R. “The Cactis Project: Database Support for Software Environments.” IEEE Transactions on Software Engineering 14, 6 (June 1988), pp. 709–719.Google Scholar
  14. [KaChBh86]
    Katz, R., Chang, E. and Bhateja, R. “Version Modelling Concepts for Computer-Aided Design Databases.” Proc. ACM-SIGMOD Conf. (May 1986), pp. 379–386.Google Scholar
  15. [Katz90]
    Katz, R. “Toward a Unified Framework for Version Modeling in Engineering Databases.” ACM Computing Surveys 22, 4 (Dec. 1990), pp. 375–408.Google Scholar
  16. [KlScWi86]
    Klahold, P., Schlageter, G. and Wilkes, W. “A General Model for Version Management in Databases.” Proc. VLDB Conf. (Aug.1986), pp. 319–327.Google Scholar
  17. [LeCh84]
    Leblang, D. and Chase, R. “Computer-Aided Software Engineering in a Distributed Workstation Environment.” Proc. ACM SIGSOFT-SIGPLAN Symposium on Practical Software Development Environments (April 1984), pp. 104–112.Google Scholar
  18. [Lie89]
    Lie, A. et al. “Change Oriented Versioning in a Software Engineering Database.” Proc. ACM SIGSOFT Conf. on Software Engineering (1989), pp. 56–65.Google Scholar
  19. [MaLa88]
    Mahler, A. and Lampen, A. “An Integrated Toolset for Engineering Software Configurations.” Proc. ACM SIGSOFT-SIGPLAN Symposium on Practical Software Development Environments, (Nov. 1988), pp. 191–200.Google Scholar
  20. [Sci89]
    Sciore, E. “Object Specialization.” ACM Transactions on Information Systems 7, 2 (April 1989), pp. 103–122.Google Scholar
  21. [Sci91]
    Sciore, E. “Versioning and Configuration Management in an Object-Oriented Data Model.” Submitted for publication, 1991.Google Scholar
  22. [Snod87]
    Snodgrass, R. “The Temporal Query Language TQUEL.” ACM Transactions on Database Systems 12, 2 (June 1987), pp. 247–298.Google Scholar
  23. [Tan86]
    Tansel, A. “Adding Time Dimension to Relational Model and Extending Relational Algebra.” Information Systems 11, 4 (Dec. 1986), pp. 343–355.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1991

Authors and Affiliations

  • Edward Sciore
    • 1
  1. 1.Computer Science Department Boston CollegeChestnut Hill

Personalised recommendations