DB2 Version 9.7 for Linux, UNIX, and Windows

AllowInterleavedGetData CLI/ODBC configuration keyword

Specifies whether the application can call SQLGetData() for previously accessed LOB columns and maintain the data offset position from the previous call to SQLGetData() when querying data servers that support Dynamic Data Format.

db2cli.ini keyword syntax:

AllowInterleavedGetData = 0 | 1

Default setting:

Do not allow calls to SQLGetData() for previously accessed LOB columns when querying database servers that support Dynamic Data Format.

Equivalent environment or connection attribute:

SQL_ATTR_ALLOW_INTERLEAVED_GETDATA

Usage notes:

This keyword affects only connections to database servers that support Dynamic Data Format, also known as progressive streaming. The default setting of 0 does not allow applications to call SQLGetData() for previously accessed LOB columns. Specify 1 to allow applications to call SQLGetData() for previously accessed LOB columns and start reading LOB data from where the application stopped reading during the previous read.

Note that when the keyword is set to 1 to allow re-access to LOB columns, some resources on the server might not be freed upon completion of SQLGetData().

If the server does not support Dynamic Data Format, this keyword has no effect, and calls to SQLGetData() for previously accessed LOB columns are allowed.

A similar keyword exists called AllowGetDataLOBReaccess that allows applications to call SQLGetData() for previously accessed LOB columns. However, if the AllowGetDataLOBReaccess keyword is used, data position and offset information is not maintained. When the LOB column is re-accessed after interleaving, SQLGetData() starts reading data from the beginning for that LOB data column. If both AllowGetDataLOBReaccess and AllowInterleavedGetData are set for a given connection or statement, the AllowInterleavedGetData setting takes precedence over AllowGetDataLOBReaccess.