Incorrect Highlighting of Matching Column/Values in INSERT

with sql assistant 5.1.10 and MS SQL

Code:

/* Sample tests of incorrect Highlighting of Matching Column/Value Pairs in INSERT Statements */
CREATE TABLE #A (col_a INT, col_b INT, col_c INT, col_d DATETIME)

INSERT INTO #A (col_a, col_b, col_c) VALUES (1,2,3) /* OK */
INSERT INTO #A (col_a, col_b, col_c) SELECT (1,2,3) /* OK */

INSERT INTO #A (col_a, col_b, col_c) VALUES (1+1,2,3) /* Wrong (with expression 1+1) */
INSERT INTO #A (col_a, col_b, col_c) SELECT 1,2,3 /* Wrong (no brackets after SELECT) */
INSERT INTO #A (col_a, col_b, col_d, col_c) SELECT (1,2,GetDate(),3) /* Wrong (with function (expression again)) */

Could you clarify what you're asking, please? I'm a little confused.

Your second insert line is not syntactically correct with the parentheses. The fourth, which you are noting as "wrong" is correct. So perhaps you're asking something other than syntax?

Please clarify.

Cursor on 2d column in INSERT. 2d column highlighted in VALUES. Correct.

Cursor on 2d column in INSERT. 2d column highlighted in SELECT. Although this line is not syntactically correct but highlighted correctly :-)

Cursor on 2d column in INSERT. No column highlighted in VALUES. Wrong.

Cursor on 2d column in INSERT. No column highlighted in SELECT. Wrong.

Cursor on 4d column in INSERT. No column highlighted in SELECT. Wrong.

Hi, thank you for your feedback.

This behavior is by design and it is documented. In the initial implementation of the matching column/value pair highlighting function we don't support expressions, including nested function. We only support simple name/value pairs. We hope to improve this column/value pair matching function and cover more complex situations in future maintenance releases.

Aaa. It's not a bug, it's a feature :)
Waiting for new releases!