JDBC/MX 5.0 Driver for SQL/MX Programmer's Reference (SQL/MX 2.x)
javax.sql.JdbcRowSet.setPassword(String password)
javax.sql.JdbcRowSet(String url, String username,
String password)
ignored. Security privileges are the same as for
the user who invoked the Java VM.
javax.sql.JdbcRowSet.setReadOnly(...)
The read-only attribute is ignored.
javax.sql.JdbcRowSet.setEscapeProcessing(...)
Disabling escape processing has no effect
because SQL/MX parses the escape syntax.
javax.sql.JdbcRowSet.setFetchDirection(...)
The fetch direction attribute is ignored.
javax.sql.JdbcRowSet.setQueryTimeout(...)
The query time-out value is ignored. The
JDBC/MX driver does not abort execution
when the query time-out period has expired.
The following features are implemented in the JDBC/MX driver but might differ in implementation from other drivers:
Updatable Result Set
The JDBC/MX driver supports both read-only and updatable concurrency modes. The JDBC/MX driver expects the
following criteria for a result set to be updatable:
The table name of the first column in the result set is assumed to be the table to be updated. This assumption
allows queries from multiple tables also to be updatable.
The query selects the primary key columns of the table to be updated.
The JDBC/MX driver throws an SQLException when any of the following conditions occur:
The primary key columns are updated.
Any selected column has been updated since the most recent time it was read. (However, the JDBC/MX driver
does not ensure that columns in the table that are not part of the select query remain unchanged since the row
was most recently read.)
A query does not select nonnullable columns or columns that do not have a default value.
The result set is also affected in the following ways:
A deleted row is removed from the result set. The method databaseMetaData.deletesAreDetected() returns
false.
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










