JDBC Type 4 Driver 2.0 Programmer's Reference (SQL/MX 2.x)

java.sql.Connection.createStatement(...)java.sql.Connection.prepareStatement(...)
The Type 4 driver does not support the scroll-sensitive
result set type, so an SQLWarning is issued if an
application requests that type. The result set is changed to
a scroll-insensitive type.
java.sql.Connection.setReadOnly(...)
The read-only attribute is ignored.
java.sql.ResultSet.setFetchDirection(...)
The fetch direction attribute is ignored.
java.sql.Statement.setEscapeProcessing(...)
Because SQL/MX parses the escape syntax, disabling
escape processing has no effect.
java.sql.Statement.setFetchDirection(...)
The fetch direction attribute is ignored.
java.sql.Statement.setQueryTimeout(int seconds)
This is based on the JDBC Driver property
closeConnectionUponQueryTimeout value.
The following is the behavior of the JDBC Driver for the
values IGNORE/DEFAULT for the property
closeConnectionUponQueryTimeout:
IGNORE = Any value (> 0) set by calling
Statement.setQueryTimeout() has no effect.
The Statement continues to block the current thread until
the statement is run.
DEFAULT = This is the value set if the property is not
specified. Any value (> 0) set by calling the
Statement.setQueryTimeout() causes an
SQLException to be raised when this is the value.
HP Extensions
Internationalization of Messages
The following HP extensions to the JDBC standard are implemented in the Type 4 driver.
Internationalization of Messages
The Type 4 driver is designed so that Java messages can be adopted for various languages. The error messages 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.
For details, see Localizing Error and Status Messages.
Conformance of DatabaseMetaData Methods' Handling of Null Parameters
This topic describes how the Type 4 driver determines the value of null parameters passed as a parameter value on DatabaseMetaData methods. Since other vendors might
implement the JDBC specification differently, this information explains the Type 4 driver results on the affected queries.
This implementation applies to methods that take parameters that can represent a pattern. The names of these parameters have the format:
attributePattern
The many methods of the java.sql.DatabaseMetaData class are affected; for example, the getColumns() method.