[
https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848534#comment-15848534
]
Knut Anders Hatlen commented on DERBY-6445:
-------------------------------------------
I cannot recall what I said about setNull(), and I don't think anything is
needed there. As to getObject(), even if this conversion is only mentioned in
the conversion tables for setObject(), [the spec for
getObject()|http://docs.oracle.com/javase/8/docs/api/java/sql/ResultSet.html#getObject-int-java.lang.Class-]
says:
"At a minimum, an implementation must support the conversions defined in
Appendix B, Table B-3 and conversion of appropriate user defined SQL types to a
Java type which implements SQLData, or Struct. Additional conversions may be
supported and are vendor defined."
So it sounds like we're free to add more conversions, and I think these ones
make sense.
> 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
> Attachments: Derby-6445.html, Derby-6445.html
>
>
> 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
(v6.3.15#6346)
