[
https://issues.apache.org/jira/browse/IBATIS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576420#action_12576420
]
Ryan Shelley commented on IBATIS-493:
-------------------------------------
I stand corrected and apologize for my insinuation. I don't intend it to do
everything for me, but the purpose of listing "improvements" are for people to
see value in the software, and want to see it succeed by providing input,
that's all. If it's a feature of iBATIS that no one is comfortable including
in Abator, then so be it. Having the ability to extend the model object from a
superclass helps resolve this problem (by creating a superclass that contains a
List of models), so that may just be enough.
> 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.
