[
https://issues.apache.org/jira/browse/DERBY-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143185#comment-13143185
]
Knut Anders Hatlen commented on DERBY-5488:
-------------------------------------------
If that works, it sounds reasonable (and more consistent). If not, I think it's
fine to leave it as it is. Since EmbedPreparedStatement169 does not implement
setBigDecimal(), some more changes may be necessary.
By the way, does setObject(BigInteger) work on CallableStatement now? If we use
the setObjectConvert() override, I think we need an override in
EmbedCallableStatement20 too. If we push the logic down to
EmbedPreparedStatement again, it should probably work automatically. Might be
worth a test case to verify that both PreparedStatement and CallableStatement
work correctly, though.
> Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc.
> -----------------------------------------------------------------------
>
> Key: DERBY-5488
> URL: https://issues.apache.org/jira/browse/DERBY-5488
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: JDBC_4.1_Supplement.html,
> derby-5488-01-aa-objectMappingAndConversion.diff,
> derby-5488-02-aa-fixBigInteger.diff
>
>
> In addition to the JDBC 4.1 bits which were visible in the Java 7 javadoc, a
> couple other items appear in the JDBC 4.1 Maintenance Review spec. This spec
> has been published on the JCP website at
> http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-eval-spec/index.html. I
> will attach a functional spec for the remaining bits.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
