Why work with Oracle and not an Object Oriented Database Management System?
An Object Database Management System handles persistent storage of C++ classes primarily. It generally implements part (but not all) of the emerging standard of the Object Database Management Group (ODMG). It may also provide support for persistency of objects in other OO languages such as Smalltalk and, recently emerging, Java. In order to achieve the transparent storage of your C++ objects you have to make your C++ classes inherit from some base class which the OODB vendor provides and in doing this you tightly couple your application to the vendor’s particular implementation of the ODMG standards. This usually means a licence for each client application which accesses the database. It also means C++ compiler choices constrained by compatibility with the vendor’s runtime libraries and choice of compiler. If we do not want to be ‘tightly bound’ to a particular vendor database we need to provide a ‘translation’ layer between d0 application code and the database. To do this largely inva
