Rogue Wave banner
Previous fileTop of DocumentContentsIndex pageNext file
DB Access Module for Sybase User's Guide
Rogue Wave web site:  Home Page  |  Main Documentation Page

2.11 Transaction Processing

There are two ways to control transactions through Sybase Open Client Client-Library:

These techniques are described in the following sections.

2.11.1 Setting Isolation Levels

You can use the isolation() method of RWDBConnection to set the isolation level of the connection. Table 5 shows the mapping between the RWDBConnection::IsolationType argument you pass and the isolation level set on the connection.

Table 5: Setting the isolation level

RWDBConnection::IsolationType Sybase Isolation Level
Unknown Level 1 - READ COMMITTED
ANSILevel1 Level 1 - READ COMMITTED
ANSILevel2 Level 2 - REPEATABLE READ
ANSILevel3 Level 3 - SERIALIZABLE

The current isolation level can be determined by calling the function RWDBConnection::isolation() without an argument.

2.11.2 Using Transaction Control Methods

You can explicitly control transactions through the following methods:

which correspond to:

An application can add the DB Interface Module transaction methods to its code to take explicit control of its transaction blocks. Transactions may be nested and the savepoint feature is supported. The savepoint feature allows a current transaction to be partially rolled back to a marked point. The following example demonstrates the use of the DB Interface Module savepoint feature and other transaction processing methods.



Previous fileTop of DocumentContentsNo linkNext file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.