Rogue Wave banner
Previous fileTop of DocumentContentsIndexNext file

2.5 Cursors

The implementation of the RWDBCursor class in the DBTools.h++ Informix Access Library is subject to restrictions imposed by the capabilities of the Informix ODBC Driver.

Some drivers require a unique index on every table involved in every cursor operation; for example, Microsoft / Sybase SQL server. An error from the ODBC driver will result if any table lacks a unique index when required.

Scrolling cursors are available through the Informix Access Library, and are implemented in the access library by setting the SQL_ATTR_CURSOR_SCROLLABLE statement attribute to SQL_SCROLLABLE. This is done automatically when a cursor of type RWDBCursor::Scrolling is requested.

To allow for the use of scrollable cursors, you must override default Informix settings by modifying your Informix ODBC Drive Data Source (DSN) configuration.

See the Informix ODBC Driver Programmer's Manual for details.

Scrolling cursors and sequential cursors act differently in respect to large blob and string data. Scrolling cursors are not able to fetch large blob or string data. For scrolling cursors, memory is allocated and bound to receive the column data. Data will be fetched only up to the size of the allocated memory. There are RWDBInformixEnvironmentHandle member functions that control the size of these allocations. Sequential cursors are not restricted in this way.


Previous fileTop of DocumentContentsIndexNext file

©Copyright 2000, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.