[
https://issues.apache.org/jira/browse/DERBY-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463748
]
Daniel John Debrunner commented on DERBY-2210:
----------------------------------------------
Foundation 1.1 adds BigDecimal which breaks the assumption made by the current
Derby JSR169 code that BigDecimal is not available. The combination of running
with BigDecimal and JSR169 causes some issues in the code where SQLDecimal is
used as the type for DECIMAL and tries to get/set values using
get/setBigDecimal which are not supported by JSR 169.
Dropping Foundation 1.0 support will allow use of BigDecimal as the underlying
type for the internal DECIMAL data type thus dropping Derby's BigInteger
implementation, but a split between the JDBC 3.0 and JSR 169 type will continue
to be needed, due to the lack of setBigDecimal and getBigDecimal. This then
requires some code shuffling in the datatypes implementation.
> Change the base J2ME level to CDC/Foundation 1.1
> ------------------------------------------------
>
> Key: DERBY-2210
> URL: https://issues.apache.org/jira/browse/DERBY-2210
> Project: Derby
> Issue Type: Sub-task
> Components: Build tools, Services
> Reporter: Daniel John Debrunner
>
> Foundation 1.1 maps to a subset of JDK 1.4 so might be a better base for J2ME
> once JDK 1.3 support is removed, since Foundation 1.0 is based upon JDK 1.3.
> Foundation 1.1 is backward compatible with 1.0, so JSR169 is supported.
> Foundation 1.0 (JSR219) went final 19 Aug, 2005.
> http://jcp.org/en/jsr/detail?id=219
> Would allow use throughout the codeline initCause() for Throwable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
