camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Camel Guy (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7904) JDBC component: Support for multiple resultSets
Date Wed, 19 Nov 2014 16:45:35 GMT


Camel Guy commented on CAMEL-7904:

The main problem is that PostgreSQL doesn't let you specify the schema on the connection properties.

Please see:

The beta 9.4 driver will not add this feature. Therefore, I think using Postgres with a connection
pool is just a headache, especially since my app determines the database name, schema, etc.
at run time. I use recipientList and dynamically generate the "to" jdbc: url.

> JDBC component: Support for multiple resultSets
> -----------------------------------------------
>                 Key: CAMEL-7904
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.14.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.
> 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.

This message was sent by Atlassian JIRA

View raw message