ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-11511) SQL: Possible bug with parameters passing for complex DML queries
Date Wed, 20 Mar 2019 12:04:00 GMT

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

Vladimir Ozerov updated IGNITE-11511:
-------------------------------------
    Ignite Flags:   (was: Docs Required)

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

Mime
View raw message