[
https://issues.apache.org/jira/browse/CAMEL-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728424#comment-13728424
]
Zemian Deng commented on CAMEL-6366:
------------------------------------
Actually I still have few more questions.
I see camel-mybatis did not implements the {{SelectMap}}, so I assume you don't
want that in this camel-sql yet?
I also have a question on the {{SelectOne}} implementation. Now with
camel-mybatis, it's the MyBatis that will auto convert a single result object
into an Object as part of their xml mapping, but for camel-sql, we don't have
this mapping feature. So what exactly do we return when user use query such as
{{select * from project where id=101}}? Just a plain Map object?
For {{SelectOne}} should I assume that if result set has only one column, we
simply return that Object as it, but if it has more than one, we return a Map?
> SQL component - Add option to dictate if output is list, object or map
> ----------------------------------------------------------------------
>
> Key: CAMEL-6366
> URL: https://issues.apache.org/jira/browse/CAMEL-6366
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
> Reporter: Claus Ibsen
> Fix For: 2.12.0
>
> Attachments: CAMEL-6366.patch
>
>
> When using the sql component, the output is always a List<Map>.
> It would be nice if you could configure an option to say its a
> - selectForObject
> - selectForList
> - selectForMap
> Like MyBatis can do.
> Also we can consider having a way to store the output on a header instead of
> altering the body.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
