JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

An inserted row is added to the result set at the current cursor position. The method
databaseMetaData.insertsAreDetected() returns true.
Batch Updates
The batch update facility allows a Statement object to submit a set of heterogeneous update, insert, or
delete commands together as a single unit to the database. This facility also allows multiple sets of
parameters to be associated with a
PreparedStatement object.
When the autocommit mode is enabled, the JDBC/MX driver commits the updates only when all commands
in the batch succeed. If any command in the batch fails, the updates are rolled back in both autocommit
and nonautocommit mode.
With the BatchUpdate Exception handling improvements support, JDBC driver now continues processing the
remaining jobs in the batch even after BatchUpdateExceptions. If there is any Batch exceptions
encountered during the execution, the exception is queued up and the remaining batch commands are
executed. At the execution completion of all elements in the batch the queued exceptions are thrown. The
user application must handle, commit, or rollback of batch transaction on an exception. By this, re-
execution of entire jobs is avoided. However, for any TMF errors, that results in transaction failure, cannot
be addressed by this enhancement.
DatabaseMetaData Calls
For the DatabaseMetaData calls, specify the catalog and schema values. If you do not specify these values,
the JDBC/MX driver uses the following default values:
catalog = NONSTOP_SQLMX_NSK;
schema = PUBLIC_ACCESS_SCHEMA;
HP Extensions
The following HP extensions to the JDBC standard are implemented in the JDBC/MX driver.
Interval Data Type
The interval data type is not a generic SQL type defined in the Java 2 JDBC 3.0 Specification, but SQL/MX
supports the
interval data type. To allow JDBC applications for SQL/MX to access the interval data type,
the JDBC/MX driver maps it to the
Types.OTHER data type. The JDBC/MX driver enables the getObject() and
getString() methods of the ResultSet interface, and the setObject() and setString() methods of the
PreparedStatement interface, to access this data type. The interval data type is always accessed as a
String object. The JDBC/MX driver also allows escape syntax for interval literals.
Internationalization
The JDBC/MX driver is designed so that Java messages can be adopted for various languages. The error
messages in JDBC/MX components are stored outside the source code in a separate property file and
retrieved dynamically based on the locale setting. The error messages in different languages are stored in
separate property files based on the language and country. This extension does not apply to all messages
that can occur when running JDBC applications.