A Run-time environment for an object-oriented database management system

Ankara : The Department of Computer Engineering and Information Sciences and the Institute of Engineering and Sciences of Bilkent Univ. , 1989.Thesis (Master's) -- Bilkent University, 1989.Includes bibliographical references leaves 97-100.In this thesis, an object-oriented query processor, a database language executer, and the protocols for the system- defined classes are designed and implemented. The designed and implemented database language completely fulfills the requirements of the object-oriented paradigm. Query processing functions are implemented through the message passing paradigm, which results in a uniform treatment of data manipulation and query processing functions. The run-time environment also supports the implementation of inheritance mechanism, class hierarchy maintenance, instance access and modification, and access to class definitions.Yengül, CanM.S

Fitting Round Objects Into Square Databases

Object-oriented systems could use much of the functionality of database systems to manage their objects. Persistence, object identity, storage management, distribution and concurrency control are some of the things that database systems traditionally handle well. Unfortunately there is a fundamental difference in philosophy between the object-oriented and database approaches, namely that of object independence versus data independence. We discuss the ways in which this difference in outlook manifests itself, and we consider the possibilities for resolving the two views, including the current work on object-oriented databases. We conclude by proposing an approach to co-existence that blurs the boundary between the object-oriented execution environment and the database. 1. Introduction Consider an environment for running object-oriented applications. There are a number of object management issues that should ideally be directly supported by the environment: persistence, creation and des..

16 Fitting Round Objects Into Square Databases

4. The object-oriented and database fields can try to merge their capabilities to arrive at systems which can smoothly integrate the facilities for both, without prohibiting either a purely database-oriented approach or a purely object-oriented approach to the problem. We obviously prefer the fourth solution, and we believe that it is a promising direction to pursue. This presupposes, however, an open approach, accepting ideas from a different area, and respecting the limitations and constraints that each area poses. The limitations and constraints of object-oriented systems and database systems did not arise through chance or oversight. They arose because other principles and other ideas were heavily emphasized. Finally, we should note that a discussion on whether databases should be extended, or another field should redevelop its capabilities is not new to databases. For instance, the same difficulties arose with knowledge bases. Should knowledge bases be implemented on top of databases? Should databases be extended to incorporate knowledge base ideas? Or should knowledge bases provide their own storage and retrieval facilities? This controversy has not been settled completely and we are now embarking on similar discussions concerning object-oriented systems. In the end, it is not important whether object-oriented or database ideas prevail. Rather

Fitting Round Objects Into Square Databases 1

Object-oriented systems could use much of the functionality of database systems to manage their objects. Persistence, object identity, storage management, distribution and concurrency control are some of the things that database systems traditionally handle well. Unfortunately there is a fundamental difference in philosophy between the object-oriented and database approaches, namely that of object independence versus data independence. We discuss the ways in which this difference in outlook manifests itself, and we consider the possibilities for resolving the two views, including the current work on object-oriented databases. We conclude by proposing an approach to co-existence that blurs the boundary between the object-oriented execution environment and the database. 1