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/01/17 16:24:00 UTC

[jira] [Updated] (IGNITE-10824) SQL: mixing _key and key columns in the DML queries must be disallowed

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

Vladimir Ozerov updated IGNITE-10824:
-------------------------------------
    Fix Version/s: 2.8

> SQL: mixing _key and key columns in the DML queries must be disallowed
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-10824
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10824
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Pavel Kuznetsov
>            Assignee: Pavel Kuznetsov
>            Priority: Minor
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> DML should contain either placeholder for _key (_val) or subset of key (value) columns but not both. Also we should keep in mind _key/_value aliases
> Given table with primary key column {{id}} and value column {{salary}}. Next queries should be validated to parsing error:
> {code:sql}
> INSERT INTO TEST_TABLE (_key, id, salary) VALUES (1, 2, 42);
> UPDATE TEST_TABLE SET _val = 1, salary = 2;
> {code}   



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