IBM DB2 Manual page 388

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
372
Application Programming Guide and Reference for Java
ResultSetMetaData values for IBM Data Server Driver for JDBC
and SQLJ version 4.0 and later
For the IBM Data Server Driver for JDBC and SQLJ version 4.0 and later, the
default behavior of ResultSetMetaData.getColumnName and
ResultSetMetaData.getColumnLabel differs from the default behavior for earlier
JDBC drivers.
If you need to use IBM Data Server Driver for JDBC and SQLJ version 4.0 or later,
but your applications need to return the ResultSetMetaData.getColumnName and
ResultSetMetaData.getColumnLabel values that were returned with older JDBC
drivers, you can set the useJDBC4ColumnNameAndLabelSemantics Connection
and DataSource property to DB2BaseDataSource.NO (2).
Batch updates with automatically generated keys have different
results in different driver versions
With the IBM Data Server Driver for JDBC and SQLJ version 3.52 or later,
preparing an SQL statement for retrieval of automatically generated keys is
supported.
With the IBM Data Server Driver for JDBC and SQLJ version 3.50 or version 3.51,
preparing an SQL statement for retrieval of automatically generated keys and
using the PreparedStatement object for batch updates causes an SQLException.
Versions of the IBM Data Server Driver for JDBC and SQLJ before Version 3.50 do
not throw an SQLException when an application calls the addBatch or executeBatch
method on a PreparedStatement object that is prepared to return automatically
generated keys. However, the PreparedStatement object does not return
automatically generated keys.
Initial value of the CURRENT CLIENT_ACCTNG special register
For a JDBC or SQLJ application that runs under the IBM Data Server Driver for
JDBC and SQLJ version 2.6 or later, using type 4 connectivity, the initial value for
the DB2 for z/OS CURRENT CLIENT_ACCTNG special register is the
concatenation of the DB2 for z/OS version and the value of the clientWorkStation
property. For any other JDBC driver, version, and connectivity, the initial value is
not set.
Use of LOB locators by the JDBC drivers
The IBM Data Server Driver for JDBC and SQLJ uses LOB locators internally under
the following circumstances:
v Always, for fetching data from scrollable cursors, when the data source or the
JDBC driver does not support progressive streaming
v Never, for fetching data from stored procedure output parameters
v If the fullyMaterializeLobData connection property is set to false, for fetching
data from non-scrollable cursors
The JDBC/SQLJ Driver for OS/390 and z/OS did not support LOB locators.
Support for scrollable and updatable ResultSets
The IBM Data Server Driver for JDBC and SQLJ supports scrollable and updatable
ResultSets.
™