[ https://issues.apache.org/jira/browse/IBATIS-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708453#action_12708453 ]
Jeff Butler commented on IBATIS-598: ------------------------------------ I believe this issue has been fixed already. See this mail thread for a discussion of the issue that was fixed: http://www.mail-archive.com/user-j...@ibatis.apache.org/msg13532.html Please try it with the latest version of Ibator in SVN (it hasn't been released yet). > Error in EqualsHashCodePlugin > ----------------------------- > > Key: IBATIS-598 > URL: https://issues.apache.org/jira/browse/IBATIS-598 > Project: iBatis for Java > Issue Type: Bug > Components: Tools > Environment: Found using ibator, version 1.2.1 > Reporter: Mike Wes > > In case of using an Oracle database, it is possible to have a NUMBER jdbcType > that is able to return a null value. A NUMBER(12,0) will be generated as a > Long. > What I face is that the generated equals method by EqualsHashCodePlugin > returns false when the Long value has the value null. It looks to me that > Long variable can be null in case the same variable from the other object has > also the value null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.