db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5536) Client's ResultSet#getLong does not range check when converting from a DECIMAL column
Date Wed, 07 Aug 2013 15:12:48 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-5536:
----------------------------------

    Assignee: Kathey Marsden  (was: Dag H. Wanvik)

Assign to myself for backport
                
> 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
>            Assignee: Kathey Marsden
>             Fix For: 10.9.1.0
>
>         Attachments: derby-5536-2.diff, derby-5536-2.stat, derby-5536-3.diff, derby-5536-3.stat,
derby-5536.diff, derby-5536-refactor.diff, derby-5536.stat, MissingRangeCheck.java
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message