[ 
https://issues.apache.org/jira/browse/CAMEL-13305?focusedWorklogId=210865&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-210865
 ]

ASF GitHub Bot logged work on CAMEL-13305:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Mar/19 07:10
            Start Date: 11/Mar/19 07:10
    Worklog Time Spent: 10m 
      Work Description: oscerd commented on pull request #2812: [CAMEL-13305] 
camel-sql cannot resolve nested simple expression
URL: https://github.com/apache/camel/pull/2812
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 210865)
    Time Spent: 20m  (was: 10m)

> camel-sql cannot resolve nested simple expression
> -------------------------------------------------
>
>                 Key: CAMEL-13305
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13305
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sql
>            Reporter: Radovan Netuka
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> - camel-sql cannot resolve nested simple expression
>  - For example, `to("sql:insert into T_EXAMPLE values 
> (:#$\{header.header1[${header.CamelLoopIndex}][COLUMN_NAME1]})")` is resolved 
> as `insert into T_EXAMPLE values (?][COLUMN_NAME1]})` instead of `insert into 
> T_EXAMPLE values ( ? )}`. And database driver will generate a syntax error.
>  - FYI, 
> `.setHeader("header1",simple("$\{header.header1[${header.CamelLoopIndex}][COLUMN_NAME1]})"))`
>  is resolved correctly. So probably sql-camel cannot properly parse the range 
> of simple expression.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to