[ http://issues.apache.org/jira/browse/IBATIS-260?page=comments#action_12366929 ]
Sven Boden commented on IBATIS-260: ----------------------------------- Fix that solves IBATIS-260 attached to JIRA, not checked in to SVN yet. After someone else verifies the fix and my local unit test case for it is cleaned up, I will check it in. > Hash conflict with groupBy resultMaps > ------------------------------------- > > Key: IBATIS-260 > URL: http://issues.apache.org/jira/browse/IBATIS-260 > Project: iBatis for Java > Type: Bug > Components: SQL Maps > Versions: 2.1.7 > Environment: iBatis 2.1.7 > MacOS 10.4.4 > MySQL 5.0.18 > Reporter: Stuart Piltch > Priority: Minor > Attachments: ibatis.zip > > I've found another issue that's similar to the one reported (by me) and fixed > (by Clinton) back in Jira iBatis-79 > I have pretty much the same setup as last time, but the problem now is: > 1) If there are nested groups, such as topic_category.name --> topic.name > --> count(*) > 2) If the same 2nd level name exists in more than one 1st level, such as the > same topic.name existing in more than one topic_category > then only one 2nd level name (topic.name) is used as the hash. Only the last > (or the first - haven't really checked that part) assignment is loaded. In my > example, three separate topic categories have the same topic name and only > one of the names gets assigned in the resultMap. The raw SQL query correctly > shows counts in all three categories. > Changing the topic names in the db slightly makes the problem go away. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
