camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7382) Enable retrieving auto generated keys in JDBC component when using named parameters
Date Sun, 08 Jun 2014 13:01:05 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021184#comment-14021184
] 

ASF GitHub Bot commented on CAMEL-7382:
---------------------------------------

Github user jfarrell closed the pull request at:

    https://github.com/apache/camel/pull/138


> Enable retrieving auto generated keys in JDBC component when using named parameters
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-7382
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7382
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jdbc
>         Environment: Improvement is independent from environment
>            Reporter: Pascal Klink
>            Assignee: Grzegorz Grzybek
>              Labels: patch
>             Fix For: 2.14.0
>
>         Attachments: generate_keys_with_parameters.patch
>
>
> The JDBC component is currently not capable of retrieving auto generated keys when using
named parameters. I think support for this should be added since it is no effort to implement
(the most changes in the patch are related to the test classes) and enables safe insertion
into tables with auto generated keys since prepared statements are used when the query is
filled with named parameters.
> One thing to note is that I could not run the JdbcSpringAnotherRouteTest because there
was an error when instantiating the CamelNameSpaceHandler because of a NoClassDefFoundError
for org/apache/camel/core/xml/AbstractCamelEndpointFactoryBean. I think this is because I
did not select the correct maven profile. So run this test after applying the patch to be
sure everything works fine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message