[DERBY-6000] Implement support for JDBC 4.2

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.10.1.1
• Component/s: JDBC
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 19/Nov/12 16:46
• Updated: 03/Jan/14 08:09
• Resolved: 13/Mar/13 13:18

Description

Open JDK 8 will include maintenance rev 4.2 of JDBC. The public discussion of JDBC 4.2 will take place here: http://openjdk.java.net/jeps/170. We will want to build Derby support for JDBC 4.2 after a public spec appears. At this time, it is unclear what Derby release will carry this support.

Issue Links

• is related to: DERBY-6073 Test ordering instability in StatementPoolingTest
• is related to: DERBY-6088 PreparedStatementTest42 lacks "fail" call when operation unexpectedly succeeds
• is related to: DERBY-6089 CallableStatement#registerOutParameter on client lacks check of legal types.
• is related to: DERBY-6094 Derby ignores DriverManager.setLoginTimeout()
• is related to: DERBY-6324 DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've implemented JDBC 4.2
• is related to: DERBY-6445 JDBC 4.2: Add support for new date and time classes
• is related to: DERBY-6070 Document Derby's JDBC 4.2 implementation
• is related to: DERBY-6187 Add a release note for metadata datatype changes introduced by JDBC 4.2
• relates to: DERBY-1184 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver
• relates to: DERBY-5949 Fix PropertySetter to take account of Java 8