JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

CommentsMethod
BASE_TYPE is added to the column data,
but its value is set to NULL because
SQL/MXdoes not support the base type.
java.sql.DatabaseMetaData.getUDTs(String catalog, String schemaPattern, String
tableNamePattern, int[] types)
Mimics the
DatabaseMetaData.getBestRowIdentifier()
java.sql.DatabaseMetaData.getVersionColumns()
method because SQL/MX does not
support SQL_ROWVER (a columns
function that returns the column or columns
in the specified table, if any, that are
automatically updated by the data source
when any value in the row is updated by
any transaction).
The Type 4 driver does not support the
scroll-sensitive result set type, so an
java.sql.Connection.createStatement(...)java.sql.Connection.prepareStatement(...)
SQLWarning is issued if an application
requests that type.
The result set is changed to a
scroll-insensitive type.
The read-only attribute is ignored.
java.sql.Connection.setReadOnly(...)
The fetch direction attribute is ignored.
java.sql.ResultSet.setFetchDirection(...)
Because SQL/MX parses the escape
syntax, disabling escape processing has
no effect.
java.sql.Statement.setEscapeProcessing(...)
The fetch direction attribute is ignored.
java.sql.Statement.setFetchDirection(...)
This is based on the JDBC Driver property
closeConnectionUponQueryTimeout
value.
java.sql.Statement.setQueryTimeout(int seconds
)
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” (page 76)
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
76 Type 4 Driver Compliance