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

10 Migration and Compatibility
• “JDBC Drivers” (page 85)
• “Third-Party Databases” (page 85)
• “Operating Systems” (page 85)
• “Compatibility” (page 85)
JDBC Drivers
ConsiderationsConfiguration Changes
Code
Changes
Driver You Are Migrating
From
N.A.url, catalog, schema, logging
facilities
NoJDBC Type 3 Driver
Application is not portable if using:url, catalog, schema, logging
facilities; potential property value
NoJDBC Driver for SQL/MX
(JDBC/MX), a Type 2 driver
• HP extension cpqPrepare
changes (verify using Summary of the
Type 4 Driver Properties)
• Unicode in CLOB data (not
supported)
• LOB with autocommit ON (not
supported)
Application is not portable if using
SequeLink specific features.
url, catalog, schema, logging
facilities
NoSequeLink JDBC Driver
The default file name for logging has
changed. For information, see
t4LogFile Property .
Potential property value changes
(verify using Summary of the Type 4
Driver Properties )
NoNonStop JDBC Type 4
Driver version 1.0
Third-Party Databases
Applications must be compatible with features and data types supported by SQL/MX. Any
application using specific features and data types customized for third-party databases must be
modified to work with the Type 4 driver. For features and data types supported by SQL/MX, see
the HP NonStop SQL/MX Release 3.2.1 Reference Manual.
Operating Systems
Any NonStop JDBC Type 4 driver application accessing NonStop SQL/MX can be migrated from
one supported platform to another (for example, PC to HP-UX) without any application changes.
Compatibility
The NonStop JDBC Type 4 Driver 3.1 is compatible with JDK 1.5 and SQLMX release with BLOB
support.
The java 1.6.0_18 or later versions of Oracle enforces the java.sql.Date.valueOf(String
s) method to follow the date format as "yyyy-mm-dd". The JDBC Type 4 driver throws
illegalArgumentException for the date format other than "yyyy-mm-dd".
JDBC Drivers 85