[
https://issues.apache.org/jira/browse/DERBY-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5536:
---------------------------------
Attachment: derby-5536-refactor.diff
Attaching a follow-up patch which factors out the test cases for DERBY-5536
into a separate fixture, adding "order by" to secure correct row retrieval
order.
> Client's ResultSet#getLong does not range check when converting from a
> DECIMAL column
> -------------------------------------------------------------------------------------
>
> Key: DERBY-5536
> URL: https://issues.apache.org/jira/browse/DERBY-5536
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Reporter: Dag H. Wanvik
> Fix For: 10.9.0.0
>
> Attachments: MissingRangeCheck.java, derby-5536-2.diff,
> derby-5536-2.stat, derby-5536-3.diff, derby-5536-3.stat,
> derby-5536-refactor.diff, derby-5536.diff, derby-5536.stat
>
>
> Derby's DECIMAL can contain an integer of 31 digits. This can overflow a
> long. The embedded JDBC driver catches this, but the client does not and can
> yield a corrupt long, cf enclosed repro.
--
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
