Sessions & Connections

An application can be designed to communicate with several RDBMSs at a time, each communication being represented by a connection that makes up the active part of a session. A connection can be closed and reopened using a different authentication.

Rogue Wave® DB Link implements the session concept through the class IldDbms, which is also the repository for the connection control.

IldDbmsModel, a twin class to IldDbms, is provided to develop drivers for RDBMS that aren't currently supported by Rogue Wave DB Link. It supports the same functionalities as IldDbms, plus the ability to be derived. So, in this manual, we describe the IldDbms class, which is the main one. The few differences between the two twin classes are itemized in a subsection.

This chapter is divided as follows, to reflect what this class allows:

Connection Handling through IldDbms Objects—Connecting, disconnecting, reconnecting.

Accessing the Database Schema for database schema descriptions—Several classes of descriptors exist to describe the various entities contained in the target database.

Data Definition Language (DDL)—Executing DDL and DML statements.

Transaction Control—All transactional operations, such as initiating, committing, or rolling back a transaction.

Cursor Allocation—Cursors are created on demand and then cached in a pool for reuse.

Extending the IldDbms Class—This class cannot be derived, but you can extend its functionalities under certain conditions. If you need to derive the IldDbms class, you must use its twin class, IldDbmsModel.

Use Notification—This feature lets you receive notifications from the RDBMS asynchronously.

Differences between IldDbms and IldDbmsModel Classes

Version 5.8