Home Feedback Contents

RC.Dbo Details


RC.Dbo Download

RC.Dbo Product Logo

Object oriented view on relational data

Features of RC.Dbo in detail

Being based on RC.Sql, RC.Dbo handles database access, database elements and result sets as objects. The producer and other attributes of the underlying database do not matter. RC.Sql takes their individual characteristics to a uniform representation.

What RC.Dbo is doing with it
RC.Dbo maps the content of tables to objects. A table is implemented in a so-called Dom-class. In this class for each table column a property is defined, so access (read and write) to the column is granted through this property. One instance of the Dom-class represents one data set of the table.

3-T programming
RC.Dbo takes place in the middle tier within the three-tier-model (e.g. the upper tier represents the GUI and the lower tier the database system). The middle tier consists of the business logic in the shape of algorithms and other functions.

Reusability of common table-properties
RC.Dbo is able to manage table objects as base-classes from which other table objects can be derived. For example, if some tables use the same business logic, it can be useful to derive the appropriate table objects from one common base-class (e.g. they all have the same primary key column name).

Usage within already existing data sources
RC.Dbo can interact with any existing database. In no case a change of the table design is necessary to integrate a RC.Dbo based application.

Efficient caching of data sets with foreign keys
A well known problem with the exclusively object oriented access on tables occurs, when processing data sets with a high number of foreign keys. If such a row is read from the database, all corresponding data from the linked table must be read instantly. This causes a great overhead of data. Reading many data sets would create a long delay.

RC.Dbo abandons to fetch the referenced data on reading such a row. It creates a Ref-instance for each foreign key, instead. With the first access on the referenced data using the proper Ref-instance the desired data is read completely from the database.

No compromise between performance and good usability
RC.Dbo is a union of both. The mapper class will be generated automatically by the mapper-generator. An application developer only has to take care of the properties in the Dom-class. Anything else is done by RC.Dbo.

The generated mapper class has the same performance as a hand made mapper. Overhead as with Reflection is avoided. Another benefit is, that there are no restrictions when using existing data sources as they appear with separate generators (see also Usage within already existing data sources).

Compatibility to user defined data types
RC.Dbo supports the usage of user defined data types within Dom-classes. Especially formatted date fields or unique styles of name fields are conceivable here.