[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849350#comment-17849350 ]
Richard N. Hillegas commented on DERBY-6445: -------------------------------------------- Attaching derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff. This is Philippe's patch plus some fixes for its Javadoc warnings. I will run full tests against this patch. A quick glance at the patch indicates that some methods are missing the diagnostic logging which appears in sister methods. At a minimum, the patch will need a little more tweaking to bring it into alignment with that diagnostic logging pattern. Touches the following files: {noformat} M java/org.apache.derby.client/org/apache/derby/client/am/ClientCallableStatement.java M java/org.apache.derby.client/org/apache/derby/client/am/ClientPreparedStatement.java M java/org.apache.derby.client/org/apache/derby/client/am/ClientResultSet.java M java/org.apache.derby.client/org/apache/derby/client/am/CrossConverters.java M java/org.apache.derby.client/org/apache/derby/client/am/Cursor.java M java/org.apache.derby.client/org/apache/derby/client/am/DateTime.java M java/org.apache.derby.client/org/apache/derby/client/am/DateTimeValue.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/DataType.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/DataValueDescriptor.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLChar.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLClob.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLDate.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTime.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTimestamp.java M java/org.apache.derby.engine/org/apache/derby/iapi/types/UserType.java M java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedCallableStatement.java M java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedPreparedStatement.java M java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedResultSet.java M java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/CallableStatementTest.java M java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/PreparedStatementTest42.java M java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/Wrapper41Test.java {noformat} > JDBC 4.2: Add support for new date and time classes > --------------------------------------------------- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC > Affects Versions: 10.10.1.1 > Reporter: Knut Anders Hatlen > Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)