Version management in an object-oriented database

  • Stanley B. Zdonik
Software Engineering Databases
Part of the Lecture Notes in Computer Science book series (LNCS, volume 244)

Abstract

We describe a database system that includes a built-in version control mechanism that can be used in the definition of any new object types. This database system is object-oriented in the sense that it supports data abstraction, object types, and inheritance.

We show how this version control mechanism can be used to manage change in the definition of a system. In particular, we show how versions of type defining objects serve to maintain consistent behavior of objects as the system evolves over time. We also show how the system can use other information such as the component-of relationship to propagate changes to the appropriate places.

The version mechanism is also used to control consistency during the process of design. The notions of consistency surface, design step, and slice are introduced. The version mechanism also gives us a way of potentially tolerating more concurrency than in conventional systems.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

7. References

  1. [ABBHS83]
    M. Ahlsen, A. Bjornerstedt, S. Britts, C. Hulten, and L. Suderland, “An Architecture for Object Management in OIS”, ACM Transactions on Office Systems, Vol. 2, No. 3, July, 1983.Google Scholar
  2. [ADP83]
    J.M. Smith, S. Fox, and T. Landers, “ADAPLEX: Rationale and Reference Manual”, second edition, Computer Corporation of America, Cambridge, Mass., 1983.Google Scholar
  3. [At84]
    M.P. Atkinson, P. Bailey, W.P. Cockshott, K.J. Chisholm, R. Morrison, “Progress with Persistent Programming” in P.M. Stoker, P.M.D. Gray, M.P. Atkinson (editors), “Databases — Role and Structure”, Cambridge University Press, Cambridge, UK, 1984.Google Scholar
  4. [BN78]
    H. Biller, E.J. Neuhold, “Semantics of Databases: The Semantics of Data Models”, Inf. Syst. 3 (1978), 11–30.Google Scholar
  5. [Bu84]
    P. Buneman, “Can We Reconcile Programming Languages and Databases?”, in P.M. Stoker, P.M.D. Gray, M.P. Atkinson (editors), “Databases — Role and Structure”, Cambridge University Press, Cambridge, UK, 1984.Google Scholar
  6. [Ch76]
    P.P.S. Chen, “The Entity-Relationship Model: Towards a Unified View of Data”, ACM TODS 1, 1, March 1976.Google Scholar
  7. [CM84]
    G. Copeland and D. Maier, “Making Smalltalk a Database System”, Proceedings of the ACM-SIGMOD International Conference on the Management of Data, Boston, Mass., June, 1984.Google Scholar
  8. [Co79]
    E.F. Codd, “Extending the Database Relational Model to Capture More Meaning”. ACM Transactions on Database Systems 4, 4 (December 1979), 397–434.Google Scholar
  9. [DZ86]
    J. Davison and S. Zdonik, “A Visual Interface for a Database with Version Management”, Proceedings of the Third International Conference on Office Information Systems, Providence, RI, October, 1986.Google Scholar
  10. [DL85]
    K.R. Dittrich and R.A. Lorie, “Version Support for Engineering Database Systems”, IBM Research Report, RJ 4769, IBM Research Laboratory, San Jose, California, July, 1985.Google Scholar
  11. [E85]
    J. Estublier, “A Configuration Manager: The Adele Database of Programs”, Proceedings of the GTE Workshop on Software Engineering Environments for Programming in the Large, Harwichport, Mass., June, 1985.Google Scholar
  12. [EP84]
    E.F. Ecklund and D.M. Price, “Multiple Version Management of Hypothetical Databases”, Oregon State University, Computer Science Department, Tech. Report No. 84-40-1, July, 1984.Google Scholar
  13. [GAL83]
    A. Albano, L. Cardelli, and R. Orsini, “Galileo: A Strongly Typed Interactive Conceptual Language”, Technical Report 83-11271-2, Bell Laboratories, Murray Hill, New Jersey, July, 1983.Google Scholar
  14. [Go83]
    J. Goguen, “LIL: A Library Interconnection Language for ADA”, in “Report on ADA Program Libraries Workshop”, SRI International, 1983.Google Scholar
  15. [G81]
    A. Goldberg. Introducing the Smalltalk-80 System. Byte (August 1981), 14–26.Google Scholar
  16. [GR83]
    A. Goldberg and David Robson. Smalltalk-80: The Language and its Implementation. Addison-Wesley, 1983.Google Scholar
  17. [HM81]
    M. Hammer, D. McLeod, “Database Description with SDM: A Semantic Database Model”, ACM TODS 6, 3, September 1981, 351–387.Google Scholar
  18. [KL82]
    R.H. Katz and T.J. Lehman, “Storage Structures for Versions and Alternatives”, Computer Sciences Department, University of Wisconsin — Madison, Technical Report No. 479, July, 1982.Google Scholar
  19. [KL83]
    R.H. Katz and T.J. Lehman, “Database Support for Versions and Alternatives of Large Design Files”, Computer Sciences Department, University of Wisconsin — Madison, Technical Report, 1983.Google Scholar
  20. [KS85]
    P. Klahold, G. Schlageter, R. Unland, and W. Wilkes, “A Transaction Model Supporting Complex Applications in Integrated Information Systems”, Proceedings of the ACM-SIGMOD International Conference on the Management of Data, Austin, Texas, May, 1985.Google Scholar
  21. [LM85]
    D.B. Leblang and G.D. McLean, Jr., “Configuration Management for Large-Scale Software Development Efforts”, Proceedings of the GTE Workshop on Software Engineering Environments for Programming in the Large, Harwichport, Mass., June, 1985.Google Scholar
  22. [LDEGPWWW84]
    V. Lum, P. Dadam, R. Erbe, J. Guenauer, P. Pistor, G. Walch, H. Werner, J. Woodfill, “Designing DBMS Support for the Temporal Dimension”, Proceedings of the ACM-SIGMOD Conference on the Management of Data, June, 1984.Google Scholar
  23. [MBW80]
    J. Mylopoulos, P.A. Bernstein, H.K.T. Wong, “A Language Facility for Designing Database-Intensive Applications”, ACM Transactions on Database Systems, Vol 5, No. 2, June, 1980, pages 185–207.Google Scholar
  24. [MSOP86]
    D. Maier, J. Stein, A. Otis, A. Purdy, “Development of an Object-Oriented DBMS”, Oregon Graduate Center, Technical Report, CS/E-86-005, April, 1986.Google Scholar
  25. [PL83]
    M.L. Powell and M.A. Linton, Database Support for Programming Environments, “Engineering Design Applications”, SIGMOD Database WEek, May, 1983.Google Scholar
  26. [S81]
    D.W. Shipman, “The Functional Data Model and the Data Language DAPLEX”, ACM TODS 6, 1 (1981), 140–173.Google Scholar
  27. [Sc78]
    J.W. Schmidt, “Type Concepts for Database Definition”, in Schneiderman, B. (editor), Databases: Improving Usability and Responsiveness, Academic Press, 1978.Google Scholar
  28. [SS77]
    J.M. Smith, D.C.P. Smith, “Database Abstractions: Aggregation”, CACM 20, 6 (1977).Google Scholar
  29. [SZ86]
    A. Skarra and S. Zdonik, “The Management of Changing Types in an Object-Oriented Database”, Proceedings of the Conference on Object-Oriented Programming, Systems, and Applications, Portland, Oregon, September, 1986.Google Scholar
  30. [SZR86]
    A. Skarra, S. Zdonik, and S. Reiss, “An Object Server for an Object Oriented Database System”, Brown University, Technical Report, April, 1986.Google Scholar
  31. [TL85]
    I. Thomas and J. Loerscher, “MOSAIX — A Version Control and History Management System”, Proceedings of the GTE Workshop on Software Engineering Environments for Programming in the Large, Harwichport, Mass., June, 1985.Google Scholar
  32. [WMy77]
    H.K.T. Wong, J. Mylopoulos, “Two Views of Data Semantics: A Survey of Data Models in Artificial Intelligence and Database Management”, INFOR 15, 3 (1977), 344–382.Google Scholar
  33. [Z84]
    S.B. Zdonik, “Object Management System Concepts”, Proceedings of the Second ACM-SIGOA Conference on Office Information Systems, Toronto, Canada, June, 1984.Google Scholar
  34. [ZW86]
    S.B. Zdonik and P. Wegner, “Language and Methodology for Object-Oriented Database Environments”, Proceedings of the Nineteenth Annual International Conference on System Sciences, Honolulu, Hawaii, January, 1986.Google Scholar

Copyright information

© Springer-Verlag 1986

Authors and Affiliations

  • Stanley B. Zdonik
    • 1
  1. 1.Brown UniversityProvidenceUSA

Personalised recommendations