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

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
c
loseConnectionUponQueryTimeout value.
The following is the behavior of the JDBC
Driver for the values IGNORE/DEFAULT for
the property c
loseConnectionUponQueryTimeout:
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.
For another example, schema is the attribute in the parameter
schemaPattern, which is a parameter to the java.sql.ResultSet.getAttributes
method.
public ResultSet getAttributes(String catalog,
String schemaPattern,
String typeNamePattern,
String attributeNamePattern)
throws SQLException
If the application passes a null value, the null is treated as follows:
If a parameter name contains the suffix Pattern, the null is interpreted as a % wildcard.
If the parameter name does not contain the suffix Pattern, nulls are interpreted as the default value for that parameter.
Using this example, null parameters are interpreted as follows: