Most object-oriented programming languages (OOPL) are designed without regard to data base aspects and do not support persistent objects or mechanisms to share objects. Experiences with the combination of C++ [STR86] and a relational database system (RDBS) in the development of a toolset based on the prototyping paradigm [POM88] have shown that the relational data model is not adequate to model the complex objects of the tools. In addition it has been found that the concepts like inheritance and encapsulation realized in the implementation language C++ do not go together well with the concepts incorporated in the RDBS, as for example, the set oriented data manipulation language. This has led to the decision to build persistent objects for C++ as basis for new CASE-tools.
[1]
Ming-Chien Shan,et al.
Iris: An Object-Oriented Database Management System
,
1989,
ACM Trans. Inf. Syst..
[2]
Stanley B. Zdonik,et al.
The management of changing types in an object-oriented database
,
1986,
OOPSLA 1986.
[3]
Erich Gamma,et al.
ET++—an object oriented application framework in C++
,
1988,
OOPSLA 1988.
[4]
Edward Sciore,et al.
The Vision Object-Oriented Database Management System
,
1987,
DBPL.
[5]
Bjarne Stroustrup,et al.
C++ Programming Language
,
1986,
IEEE Softw..
[6]
David Maier,et al.
Development of an object-oriented DBMS
,
1986,
OOPSLA 1986.