JDBC Type 4 Driver 1.1 Programmer's Reference

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:
catalog
the default catalog name
schemaPattern
a % wildcard and retrieves data for all schemas of the specified catalog
Type 4 Driver Conformance to SQL Data Types
JDBC Data Types
JDBC Data Types
The following table shows the JDBC data types that are supported by Type 4 driver and their corresponding SQL/MX data types:
JDBC Data Type Support by JDBC Type 4 Driver for NonStop SQL/MX SQL/MX Data Type
Types.Array
No N.A.
Types.BIGINT
Yes LARGEINT
Types.BINARY
Data type is mapped by SQL/MX . Data type varies from that used for table creation. CHAR(n)¹
Types.BIT
Data type is mapped by SQL/MX . Data type varies from that used for table creation. CHAR(1)
Types.BLOB
Yes LARGEINT
Types.CHAR
Yes CHAR(n)
Types.CLOB
Yes LARGEINT