On behavioral schema evolution in object-oriented databases

  • Magdi M. A. Morsi
  • Shamkant B. Navathe
  • John Shilling
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 779)

Abstract

This paper describes the effect of schema evolution operations on the implementation of methods. The effect of these operations is captured as temporary inconsistencies. Extensions for handling these temporary inconsistencies in our Graphical Object-Oriented Schema Environment prototype, called GOOSE are described. In GOOSE, the schema information is maintained as a set of system objects of system defined classes. In order to maintain these temporary inconsistencies, the system classes have been augmented with two classes, namely Uses and Stubs, as specialization of the system class Class. Furthermore, schema evolution operations for explicitly resolving these inconsistencies are defined.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    J. Banerjee, W. Kim, H.-J. Kim, and H. Korth, “Semantics and implementation of schema evolution in object-oriented databases,” in Proceedings of the International Conference on Management of Data, San Francisco, CA, pp. 311–322, May 1987.Google Scholar
  2. 2.
    D. Penney and J. Stein, “Class modification in the GemStone Object-Oriented DBMS,” in Proceedings of the Second Conference on Object Oriented Programming Systems, Languages, and Applications, Kissimmee, Florida, pp. 111–117, October 1987.Google Scholar
  3. 3.
    G.-T. Nguyen and D. Rieu, “Expert database support for consistent dynamic objects,” in Proceedings of the Thirteenth Conference on Very Large Databases, Brighton, UK, pp. 493–500, September 1987.Google Scholar
  4. 4.
    G.-T. Nguyen and D. Rieu, “Schema evolution in object-oriented database systems,” Tech. Rep. TR No. 947, INRIA Laboratoire de Genie Informatique, France, December 1988.Google Scholar
  5. 5.
    R. Zicari, “A framework for schema updates in an object-oriented database system,” in Proceedings of the Seventh International Conference on Data Engineering, Kobe, Japan, pp. 2–13, April 1991.Google Scholar
  6. 6.
    C. Delcourt and R. Zicari, “The Design of an Integrity Consistency Checker (ICC) for an Object-Oriented Database System,” in Proceedings of the European Conference on the Object-Oriented Programming, P. America, ed., Geneva, Switzerland, pp. 95–117, Springer-Verlag, July 1991.Google Scholar
  7. 7.
    M. Morsi, S. Navathe, and H.-J. Kim, “A Schema Management and Prototyping Interface for an Object-Oriented Database Environment,” in Proceedings of the IFIP working conference on the Object Oriented Approach in Information Systems, Quebec City, Canada, pp. 157–181, North Holland Publishers, Inc., October 1991.Google Scholar
  8. 8.
    M. Morsi, S. Navathe, and H.-J. Kim, “An Extensible Object-Oriented Database Testbed,” in Proceedings of the Eighth International Conference on Data Engineering, Pheonix, Arizona, pp. 150–157, February 1992.Google Scholar
  9. 9.
    M. Morsi, Extensible Object-Oriented Database with Dynamic Schemas. PhD thesis, College of Computing, Georgia Institute of Technology, Atlanta, GA, September 1992.Google Scholar

Copyright information

© Springer-Verlag 1994

Authors and Affiliations

  • Magdi M. A. Morsi
    • 1
  • Shamkant B. Navathe
    • 2
  • John Shilling
    • 2
  1. 1.IBM Santa Teresa LaboratorySan JoseUSA
  2. 2.College of ComputingGeorgia TechAtlantaUSA

Personalised recommendations