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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: sql
• Assignee: Pavel Kuznetsov
• Reporter: Pavel Kuznetsov
• Created: 26/Dec/18 12:22
• Updated: 25/Jan/19 13:58
• Resolved: 25/Jan/19 13:56

Description

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:

INSERT INTO TEST_TABLE (_key, id, salary) VALUES (1, 2, 42);
UPDATE TEST_TABLE SET _val = 1, salary = 2;

Issue Links

• is related to: IGNITE-4363 Inner properties mutation broken in SQL UPDATE
• is related to: IGNITE-10645 SQL properties ownership flag should be set at configuration parsing, not query execution.
• links to: GitHub Pull Request #5821
• links to: GitHub Pull Request #5918