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.
Properties that control the use of multi-row FETCH
Before version 3.7 and version 3.51 of the IBM Data Server Driver for JDBC and
SQLJ, multi-row FETCH support was enabled and disabled through the
useRowsetCursor property, and was available only for scrollable cursors, and for
IBM Data Server Driver for JDBC and SQLJ type 4 connectivity to DB2 for z/OS.
Starting with version 3.7 and 3.51:
v For IBM Data Server Driver for JDBC and SQLJ type 2 connectivity on DB2 for
z/OS, the IBM Data Server Driver for JDBC and SQLJ uses only the
enableRowsetSupport property to determine whether to use multi-row FETCH
for scrollable or forward-only cursors.
v For IBM Data Server Driver for JDBC and SQLJ type 4 connectivity to DB2 for
z/OS or DB2 Database for Linux, UNIX, and Windows, or IBM Data Server
Driver for JDBC and SQLJ type 2 connectivity on DB2 Database for Linux,
UNIX, and Windows, the IBM Data Server Driver for JDBC and SQLJ uses the
enableRowsetSupport property to determine whether to use multi-row FETCH
for scrollable cursors, if enableRowsetSupport is set. If enableRowsetSupport is
not set, the driver uses the useRowsetCursor property to determine whether to
use multi-row FETCH.
JDBC 1 positioned updates and deletes and multi-row FETCH
Before version 3.7 and version 3.51 of the IBM Data Server Driver for JDBC and
SQLJ, multi-row FETCH from DB2 for z/OS tables was controlled by the
useRowsetCursor property. If an application contained JDBC 1 positioned update
or delete operations, and multi-row FETCH support was enabled, the IBM Data
378 Application Programming Guide and Reference for Java
™
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To Next Page
Loading...
Need help?
General