[DERBY-310] Document and/or change Derby client code to match behavior with Embedded driver where possible.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.6.1.0
• Component/s: Documentation, JDBC
• Assignee: Unassigned
• Reporter: Satheesh E. Bandaram
• Created: 24/May/05 05:15
• Updated: 02/May/13 02:30
• Resolved: 17/Aug/09 11:12

Description

[NOTE: This meta-issue has been replaced by the "Bug behavior facts" flag "Embedded/client difference" DagW 2009-08-17]

There are some behavior differences between Derby client and embedded JDBC drivers. Change Derby client code to match embedded behavior or document some of these differences.

This JIRA entry is a top level task for tracking these issues. Individual subtasks should be created or existing tasks linked to this Jira entry, but no specific feature content added here. Please create subtaks to this Jira entry to track any known differences documentation issues or tasks needed to investigate this issue.

Kathey Marsden also started this effort to compile known differences.(http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/[e-mail]%3e)

The Derby community voted that client should match embedded where possible.
See:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200505.mbox/[e-mail]%3e

Issue Links

• incorporates: DERBY-931 Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
• incorporates: DERBY-2423 Embedded and client differ on ResultSetMetaData.isCurrency() value for DECIMAL and NUMERIC columns
• incorporates: DERBY-160 Foreign key constraint failure closes the cursors in embedded mode but not in Network Server mode
• incorporates: DERBY-911 Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client.
• incorporates: DERBY-4778 In Client mode, holdable resultset cursor used in positioned update shouldn't access row with autocommit=true
• incorporates: DERBY-1098 isDefinitelyWritable on client returns true where embedded returns false
• incorporates: DERBY-1370 Embedded and client driver differ in the holdability reported inside a global transaction for statements that were created with HOLD_CURSORS_OVER_COMMIT outside the transaction
• incorporates: DERBY-2651 Embedded and client behave differently for IJ command "show indexes"
• incorporates: DERBY-3171 ResultsetMetadata.isNullable returns different value for networkserver/client vs. embedded on some columns after a call to DatabaseMetaData.getAttributes()
• incorporates: DERBY-307 create=true in client connect throws ex if database exists
• incorporates: DERBY-501 Client and embedded drivers differ on invoking a procedure that returns a single Dynamic resultSet using CallableStatement.executeQuery()
• incorporates: DERBY-525 getAsciiStreamshould replace non-ASCII characters with 0x3f, '?' to match embedded
• incorporates: DERBY-596 jdbcapi/resultsetStream.java fails in DerbyNetClient Framework
• incorporates: DERBY-638 Network driver setTransactionIsolation() causes a commit, but does not complete it locally
• incorporates: DERBY-728 Unable to create databases whose name containg Chinese characters through the client driver
• incorporates: DERBY-1493 EmbeddedDriver does not implement PreparedStatement.setNull(int, int, String)
• incorporates: DERBY-1610 Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver
• incorporates: DERBY-2064 Network client setTransactionIsolation() commits any active transactions
• incorporates: DERBY-2084 getTransactionIsolation() in network client should not activate a transaction
• incorporates: DERBY-2531 client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.
• incorporates: DERBY-2532 Client does not return SQLException on XAConnection.getXAResource() on a closed connection, Embedded does
• incorporates: DERBY-2652 Clob.setCharacterStream differs between embedded and client driver
• incorporates: DERBY-3856 difference between Embedded vs DerbyNetClient in format of return from timestamp(cast(? as varchar(32)))
• incorporates: DERBY-461 Network Client Driver 'password=' behaviour is different from Embedded Driver
• incorporates: DERBY-694 Statement exceptions cause all the connection's result sets to be closed with the client driver
• incorporates: DERBY-965 DatabaseMetadata method supportsResultSetConcurrency returns wrong result on network client
• incorporates: DERBY-1440 jdk 1.6 client driver omits SQLStates and chained exceptions in error messages
• incorporates: DERBY-1484 Client and embedded behave differently when the table name is null in DatabaseMetaData methods
• incorporates: DERBY-1494 PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
• incorporates: DERBY-1516 Inconsistent behavior for getBytes and getSubString for embedded versus network
• incorporates: DERBY-2065 Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.
• incorporates: DERBY-2601 Server SQLException error codes are not returned to client
• incorporates: DERBY-2692 Client driver doesn't chain exceptions received from the server
• incorporates: DERBY-2771 Unhelpful error message provided when accesing Blob after commit in the client driver
• incorporates: DERBY-3436 Embedded closes all open ResultSets on failure in auto-commit mode, whereas client keeps them open
• incorporates: DERBY-3898 Blob.setBytes differs between embedded and client driver when the specified length is invalid
• incorporates: DERBY-1657 Align error reporting in the client driver and embedded driver for streaming errors through the JDBC API
• incorporates: DERBY-1312 refreshRow behavior not the same in Derby client and embedded drivers
• incorporates: DERBY-3851 Client and embedded differ on sending StatementEvent on Connection.close()
• incorporates: DERBY-2113 The maximum number of statements per batch differ between client and embedded
• incorporates: DERBY-31 Statement.setQueryTimeout() support.
• incorporates: DERBY-1658 Too short streams passed in through JDBC are handled differently in client and embedded
• incorporates: DERBY-4767 Detailed prompt for Error XCL16 is different between Client and Embed
• incorporates: DERBY-4777 Different behavior in Client and Embedded modes when update on an invalid cursor
• incorporates: DERBY-572 Add support for Clob.setCharacterStream(), Clob.setAsciiStream()and Blob.setBinaryStream in embedded, it is already supported in client.
• incorporates: DERBY-1267 Add setCreateDatabase and setShutdownDatabase methods to datasource classes in client
• incorporates: DERBY-1371 Remove test harness special handling for handle varying client column widths
• incorporates: DERBY-2653 Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
• incorporates: DERBY-3114 Harmonize sql state thrown when closing a connection with pending transaction between net end embedded drivers
• incorporates: DERBY-3853 Behaviour of setTypeMap() differs between embedded and client
• incorporates: DERBY-2453 client and embedded differ for return value for PreparedStatement.getMetaData if there is no ResultSet returned
• is blocked by: DERBY-211 Network Server returns no result sets for a procedure call that returns no result
• is blocked by: DERBY-254 SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible
• is related to: DERBY-142 ResultSetMetaData.isReadOnly() also returns wrong results
• is related to: DERBY-2301 Documentation of different executeBatch error handling between embedded and DerbyNetClient needed
• relates to: DERBY-1500 PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode
• relates to: DERBY-1501 PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
• relates to: DERBY-477 JDBC client and embedded drivers differ wrt API subset supported