empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Commented] (EMPIREDB-171) ObjectUtils.compareEquals fails on BigDecimal
Date Tue, 02 Oct 2012 11:43:09 GMT

    [ https://issues.apache.org/jira/browse/EMPIREDB-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467626#comment-13467626

Francis De Brabandere commented on EMPIREDB-171:

I wonder if there are any cases where compareTo would result in unexpected behaviour...

This is the javadoc for the equals() method
Compares this BigDecimal with the specified Object for equality. Unlike compareTo, this method
considers two BigDecimal objects equal only if they are equal in value and scale (thus 2.0
is not equal to 2.00 when compared by this method).
> ObjectUtils.compareEquals fails on BigDecimal
> ---------------------------------------------
>                 Key: EMPIREDB-171
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-171
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.4.0
>            Reporter: Daniel Weidele
>            Priority: Critical
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Observed:
> When comparing a BigDecimal with internal value e.g. '50' to another BigDecimal with
internal value '50.00' ObjectUtils.compareEquals returns false as it internally forwards to
the BigDecimal.equals method, which also relies on internal BigDecimal properties such as
scale, etc.
> Expected:
> ObjectUtils.compareEquals should return true when comparing e.g. '50' to '50.00'

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

View raw message