MX 2.x)

Transactions

Transaction semantics changed in the V31 product from the previous versions of the JDBC/MX driver when the

connection is set to autocommit mode.

In previous releases, when multiple select statements were involved in a transaction in autocommit mode, the

JDBC/MX driver ended the transaction when any select statement result set was closed. In this release, the JDBC/MX

driver ends the transaction only when the result set of the select statement that started the transaction is closed.

If your application depends on the previous transaction semantics, you need to re-code the application.

nametype Property

Use of the nameType property was removed in the JDBC/MX V31 driver. This property allowed you to specify the use

of either ANSI or SHORTANSI names. SHORTANSI names are no longer allowed. The names are ANSI names.

Remove use of this feature from your applications.

Deprecated Property-Name Specification

With the JDBC/MX V31 and V32 drivers, property names used on the command line in the java -D option should

now include the prefix:

jdbcmx.

This notation, which includes the period (.), ensures that all the JDBC/MX driver property names are unique for a

Java application. For example: maxStatements becomes

jdbcmx.maxStatements

For application migration purposes, the JDBC/MX V31 and V32 drivers allow the deprecated property-name

specification on the command line.

The property names passed to JDBC/MX V31 and V32 driver methods in a Properties object do not require the prefix.

Summary of Deprecated Property-Name

Specifications for Use in the Command Line

Deprecated

Property-Name

Specification

New Property-Name

Specification

catalog jdbcmx.catalog

schema jdbcmx.schema

mploc jdbcmx.mploc

maxPoolSize jdbcmx.maxPoolSize

minPoolSize jdbcmx.minPoolSize

maxStatements

jdbcmx.maxStatements