[
https://issues.apache.org/jira/browse/IBATIS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576176#action_12576176
]
Jeff Butler commented on IBATIS-493:
------------------------------------
This has been discussed on the lists many times. I did a serious investigation
of this topic sometime back and its quite complex to solve in a general way.
In fact, the situation you describe would better be solved by a groupBy rather
than a resultMap select. But this case is only the most simple of cases - this
problem can quickly balloon into a very complex problem indeed. What if a
table is linked to more than one other table (as is quite common)? What if the
linking goes many layers deep? Also, some of the limitations of iBATIS itself
add to the difficulties.
In the end, my feeling about this is that the work of configuring Abator to
deal with table relationships is more difficult than simply extending the
generated result maps and objects. Everything you describe can be accomplished
by extending generated objects - which is very simple.
I'll leave this open for now to allow additional comments from the interested
parties.
> Add Abator config to utilize resultMap "select" attribute
> ---------------------------------------------------------
>
> Key: IBATIS-493
> URL: https://issues.apache.org/jira/browse/IBATIS-493
> Project: iBatis for Java
> Issue Type: Improvement
> Components: Tools
> Reporter: Ryan Shelley
> Priority: Minor
>
> The iBATIS SQLMaps resultMap element supports a "select" attribute that maps
> to another "select" statement to nest complex resultMaps. It would be
> helpful to allow Abator to provide a configuration option to the "table"
> element that would map two tables together by Primary Key, ultimately,
> generating a resultMap implementing the "select" attribute. This would be
> helpful for tables where two tables are intrinsically linked. The only way
> around this currently is to create a custom SQLMap, ResultMap, Model, and DAO
> method outside the scope of Abator, which could become out of sync as Abator
> is used to rebuild Models, Maps, and Statements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
