[
https://issues.apache.org/jira/browse/CAMEL-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169599#comment-14169599
]
Camel Guy edited comment on CAMEL-7904 at 11/19/14 4:49 PM:
------------------------------------------------------------
I went through the Statement JDBC interface and it appears that there is no way
to know how many ResultSets will be returned. You have to process each
ResultSet until there are no more. So the JDBC component can not simply return
the "last" ResultSet. Instead, it needs to be told how many result sets to
ignore.
was (Author: camelguy):
I just went through the Statement JDBC interface and it appears that there is
no way to know how many ResultSets will be returned. You have to process each
ResultSet until there are no more. So the JDBC component can not simply return
the "last" ResultSet. Instead, it needs to be told how many result sets to
ignore.
> JDBC component: Setting the PostgreSQL schema search path
> ---------------------------------------------------------
>
> Key: CAMEL-7904
> URL: https://issues.apache.org/jira/browse/CAMEL-7904
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.13.0
> Reporter: Camel Guy
>
> For PostgreSQL it is common to run two commands in a single transaction in
> order to set the schema search path:
> set search_path to foo, public;
> select 5;
> Due to connection pooling it is desirable to combine both statements in a
> single operation.
> These types of queries don't work with the JDBC component because it only
> returns the result set for the first command (set search_path), which is
> always empty.
> The easiest solution would be an option to skip the first N result sets.
> However, if any of those result sets reported an error, an exception should
> be thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
