The table below describes the rough correspondence between the Unity
DB2 classes and the equivalent Abt provided classes. Some classes play
more than one role. Also, for some operations there exists more than
one way to code the operation.
Abt Part | Unity Equivalent Class | Comment |
AbtDatabaseManager, AbtDatabaseLogonSpec, AbtDbmSystem | UtyDB2DatabaseManager | Greatly simplified DB2 logon procedure |
AbtQuerySpec | UtyDB2SqlDescriptor, UtyDB2Statement | Uses Dictionary instead of AbtCompoundType to describe parameter types. Unity has separated the classes involved in statement preparation and execution to more closely reflect how SQL compilation works. |
AbtResultTable | UtyDB2ResultSet + subclasses | Similar behavior. ResultSets must be explicitly closed if they are not read until the last entry |
AbtDatabaseConnectionSpec | UtyDB2ConnectionDescriptor |
|
AbtDatabaseConnection | UtyDB2Connection |
|
AbtDatabase | UtyDB2Database |
|
AbtRow | UtyDB2Row |
|
AbtCompoundType | Dictionary | Used for type information for parameter description
Used for data information for parameter values |
The next few sections describe in general terms what needs to be done in order to convert the persistence framework from the IBM's Database Manager application to Unity's DB2 driver application. For detailed coding examples, please see the section entitled: Usage Examples.