[jira] [Updated] (CAMEL-7904) JDBC component: Setting the PostgreSQL schema search path

["Camel Guy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Camel Guy updated CAMEL-7904:
-----------------------------
          Description: 
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.

  was:
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.

Easiest solution is to provide a uri option to return the last result set instead of the first one. This solution would be preferable to me and would be compatible with streaming. 

A more complete solution would be an option to return all of the result sets.

    Affects Version/s:     (was: 2.14.0)
                       2.13.0
              Summary: JDBC component: Setting the PostgreSQL schema search path  (was: JDBC component: Support for multiple resultSets)

> 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)