On 27 Jun 2016 7:13 pm, "Vitalii Diravka" <[email protected]> wrote:
>
> Hi all!
>
> Recently I tried to use "ADD" on the first place of a new custom sql
> statement and found that non-reserved words can't be placed on the first
> place of the statement.
> But it is ok if a non-reserved word is placed on the other places of a
> statement.
>
> Can anybody explain me the reason of this parser behavior?
>
Reserved tokens help define the starting state of the parser. If non
reserved keywords were allowed as the first token, there would be ambiguity
as to which rule to apply.
