You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/20 03:23:00 UTC

[jira] [Commented] (IGNITE-11511) SQL: Possible bug with parameters passing for complex DML queries

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

Ignite TC Bot commented on IGNITE-11511:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3358516&amp;buildTypeId=IgniteTests24Java8_RunAll]

> SQL: Possible bug with parameters passing for complex DML queries
> -----------------------------------------------------------------
>
>                 Key: IGNITE-11511
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11511
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Kuznetsov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> See methods {{IgniteH2Indexing.executeSelectLocal}} and {{IgniteH2Indexing.executeSelectForDml}}. They both could be invoked for {{SELECT}} statements extracted from DML. 
> But notice how parameters are passed: it seems that we may pass parameters from DML statement unchanged, which is illegal. E.g. consider the following DML:
> {code}
> UPDATE table SET x=? WHERE x=?
> {code}
> In this case SELECT statement should get only the second parameter.
> Need to create tests to confirm that this is the case and make necessary fixes if needed.



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