You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/08 11:07:00 UTC
[jira] [Created] (IGNITE-11511) SQL: Possible bug with parameters
passing for complex DML queries
Vladimir Ozerov created IGNITE-11511:
----------------------------------------
Summary: 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
Fix For: 2.8
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)