Restrictions and Interpretations of JDBC Standards
The jConnect implementation of JDBC deviates from the JDBC standards.
- Unsupported JDBC 4.0 Specification Requirements
Review the JDBC 4.0 statements that are not supported in this release.
- Use Connection.isClosed and IS_CLOSED_TEST
jConnect offers a default interpretation of the isClosed method that differs from the behavior defined in the JDBC 4.0 specification.
- Statement.close with Unprocessed Results
The JDBC specification deos not clearly address how a driver should behave when you call Statement.execute and later call close on that same statement object without processing all of the results (update counts and ResultSets) returned by the Statement.
- Adjustments for Multithreading
Several threads simultaneously call methods on the same Statement instance, CallableStatement, or PreparedStatement, which Sybase does not recommend you must manually synchronize the calls to the methods on the Statement; jConnect does not do this automatically.
- ResultSet.getCursorName
JDBC drivers generate a cursor name for any SQL query so that a string can always be returned. However, jConnect does not return a name when ResultSet.getCursorName is called.
- Execute Stored Procedures
Executing a stored procedure in a CallableStatement object that represents parameter values as question marks, you get better performance than if you use both question marks and literal values for parameters.
Created August 22, 2013. Send feedback on this help topic to Technical Publications:
pubs@sap.com