ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Boden (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Commented: (IBATIS-260) Hash conflict with groupBy resultMaps
Date Mon, 20 Feb 2006 21:16:25 GMT
    [ http://issues.apache.org/jira/browse/IBATIS-260?page=comments#action_12367080 ] 

Sven Boden commented on IBATIS-260:

I attached the final version of the fix for IBATIS-260 to the JIRA if anyone would want to
look over it. The fix has been verified by the original creator of the JIRA, by my, and I
also have a JUnit testcase. I plan to check it in tomorrow evening.

- new property in RequestScope to track the nested keys for hierachical groupBys
- BasicResultMap's getUniqueKey now can take a prefix and appends a "separator"

> 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-260-checkin.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 -->
>  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:
For more information on JIRA, see:

View raw message