empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Resolved] (EMPIREDB-193) DBRowSet has an equals() implementation but no hashCode() implementation.
Date Mon, 23 Sep 2013 07:25:02 GMT

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

Rainer Döbele resolved EMPIREDB-193.
------------------------------------

       Resolution: Fixed
    Fix Version/s: empire-db-2.4.2
         Assignee: Rainer Döbele

Thanks Harald for letting us know.
I have now implemented the hashCode() for DBRowSet.
                
> DBRowSet has an equals() implementation but no hashCode() implementation.
> -------------------------------------------------------------------------
>
>                 Key: EMPIREDB-193
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-193
>             Project: Empire-DB
>          Issue Type: Bug
>    Affects Versions: empire-db-2.4.1
>            Reporter: Harald Kirsch
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.4.2
>
>
> If equals() is implemented other than as object identity, hashCode() must be implemented
too. Otherwise two equal objects may have a different hash code, which violates the contract
define in java.lang.Object.
> Workaround: never use a DBRowSet as a key in a hash table and don't use java.util.Set
to unique a list of tables.

--
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