[
https://issues.apache.org/jira/browse/IBATIS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576407#action_12576407
]
Jeff Butler commented on IBATIS-493:
------------------------------------
I strongly disagree with the premise of your last comment. iBATIS has many
features that are not reflected in the code generated by Abator. This in no
way implies that we don't recommend using those features.
I suggest that you read the introductory documentation page for Abator - this
describes the purpose of the tool. We do not expect the tool to do
*everything* for you - you must still do a little work. Abator is for cutting
down a lot of the nuisance work. You might also look at the "philosophy" page.
We talk more about the usage of the tool there.
> 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.
