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

SQL/MX does not support the column type
for types as follows:
TYPE_CAT,
TYPE_SCHEMA,
TYPE_NAME,
SELF_REFERENCING_COL_NAME,
and REF_GENERATION.
java.sql.DatabaseMetaData.getUDTs(String catalog,
String schemaPattern, String tableNamePattern,
int[] types)
BASE_TYPE is added to the column data,
but its value is set to NULL because
SQL/MX does not support the base type.
java.sql.DatabaseMetaData.getVersionColumns()
Mimics the
DatabaseMetaData.getBestRowIdentifier()
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).
java.sql.DriverManager.getConnection(String url,
String usr, String password)
java.sql.DriverManager.getConnection(String url,
Properties info)
javax.sql.DataSource.getConnection(String
username, String password)
User name and password arguments are
ignored. All connections have the same
security privileges as the user who
invoked the Java VM.
java.sql.DriverManager.setLoginTImeout(...)
javax.sql.DataSource.setLoginTimeout(...)
Login time-out is ignored.
javax.sql.DataSource.setLogWriter
This method has no effect unless the
JDBC trace facility is enabled; for
information on the JDBC trace facility, see
the
NonStop Server for Java Programmer's
Reference
.
java.sql.Connection.createStatement(...)
java.sql.Connection.prepareStatement(...)
The JDBC/MX 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.ResultSetMetaData.getPrecision(int
column)
java.sql.ResultSetMetaData.getColumnDisplaySize(int
column)
For CLOB and BLOB columns, these
methods return 0 to denote an unlimited
value. According to the standard API, the
getPrecision() method and
getColumnDisplatSize() method return an
integer value, but LOB data larger than
the maximum integer value can be stored
in the database.
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.