Open andialbrecht opened 1 month ago
Removing milestone again, this is once again the ambiguity of year
, month
, etc. being a keyword and being used as an identifier. That's why the as year
variant works, this removes the ambiguity.
I'm not sure how to handle this in the parser right now, as the parser has little to none context.
@mhmtsoydam, I'm sorry, but I don't think that this gets fixed any time soon...
Better to use AS YEAR
then, thanks!
Describe the bug A SQL containing aliased function calls is parsed (and formatted) wrong when the
AS
keyword is mussing.To Reproduce
The parser identifies
year
andmonth
as keywords.Expected behavior The formatting (and parsing) of
bad_sql_alias
should be the same way as for the good ones.Versions (please complete the following information):
Additional context Add any other context about the problem here.