lotus

previous page: 9.3) Odapter/OpenODB: Odapter Language
  
page up: Object-Oriented Technology FAQ
  
next page: 9.3) Odapter/OpenODB: Odapter and Smalltalk

9.3) Odapter/OpenODB: Odapter Object Storage




Description

This article is from the Object-Oriented Technology FAQ, by Bob Hathaway rjh@geodesic.com with numerous contributions by others.

9.3) Odapter/OpenODB: Odapter Object Storage

Odapter objects are stored in the developer's
choice of relational databases. Odapter interfaces
to the underlying RDBMS through an SQL command
interface. Currently, developers can choose to
store their objects in ORACLE7 or HP ALLBASE/SQL.

The choice of RDBMS is made when a particular
database is created. The users are only limited by
the number of Odapter concurrent user licenses
purchased. This flexibility allows database
administrators to continue using their existing
administration procedures and keeps the group from
having to choose yet another database management
system.

During the initial development of an application,
developers can make rapid progress without
knowledge of the underlying relational database.
Optimization of the objects and how they are stored
in the underlying relational database is best
done during the deployment phase.

Odapter Development Environments

Odapter developers have a choice of development
environments. Whether Smalltalk, C++ or more
traditional C and C-linkable languages are used,
Odapter enables object storage in a scalable and
robust relational database. In fact, objects can be
shared between different applications, allowing
different projects to employ the best tools for the
job!

 

Continue to:













TOP
previous page: 9.3) Odapter/OpenODB: Odapter Language
  
page up: Object-Oriented Technology FAQ
  
next page: 9.3) Odapter/OpenODB: Odapter and Smalltalk