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

Unsupported SQL/MX Features
MXCI commands
SQL/MX utility commands
SQL Statements
Transaction Control statements
Prepared SQL statements (PREPARE and EXECUTE)
Resource control and optimization statements
object naming statements
alias statements
Refer to the NonStop SQL/MX documentation set for a complete list of supported features.
Unsupported SQL/MP Features
SQL/MP DDL support
Columns described with the character sets ISO8859/2 through ISO8859/9
Utility commands
Embedded-only SQL/MP statements
Transaction Control statements
Stored procedures
Refer to the NonStop SQL/MP documentation set for a complete list of supported features.
Other Unsupported Features
These features are not required for JDBC 3.0 compliance, and they are not supported by the NonStop JDBC Type 4 Driver.
Multiple result sets returned by batch statements.
Database savepoint support. (Not provided in SQL/MX )
Retrieval of auto generated keys.
Transform group and type mapping.
Relationship between connector architecture and JDBC 3.0 SPI.
Secured socket communication or encryption for the interaction between the NonStop JDBC Type 4 Driver and MXCS.
Security context (user name and password) implicit propagation from AppServer to the NonStop JDBC Type 4 Driver.
IPV6 protocol stack. (IPV6 addressing is emulated over IPV4 on the MXCS server side)
Restrictions
The Type 4 driver supports only database features that are supported by NonStop SQL/MX and SPJ. Therefore, the Type 4 driver is not fully
compliant with JDBC 3.0 specifications.
The Type 4 driver depends on MXCS for all server side manageability related features.
The system running an R 3.1 version of NonStop JDBC Type 4 Driver 3.1 cannot connect to a NonStop system running an R 2.x version of
MXCS server objects. When you try to connect an R 3.1 version of NonStop JDBC Type 4 Driver to an R 2.x version of MXCS server
objects, the behavior is unpredictable.
java.sql.connection.setAutoCommit(boolean autoCommit())
Sets this connection's auto-commit mode to the given state (true or false). If a connection is in auto-commit mode, then its SQL statements will
be executed and committed as individual transactions. Otherwise, its SQL statements are grouped into transactions that are terminated by a call
to either the method commit or method rollback. By default, new connections are in auto-commit mode. If the value of auto-commit is changed
in the middle of a transaction, the current transaction is committed. If
setAutoCommit is called and the value for auto-commit is not changed from
its current value, it is treated as a NO-OP.
Prev Up Next
Chapter 7. Module File Caching (MFC) Home Chapter 9. Tracing and Logging Facilities
Part Number
663860-001
Legal Notices