This PR contains only sqlparser changes to fix the open issue. During debugging we faced that sqlparser flow has incorrect flow for parsing statements as WHERE "column" = 'value' as it looks on value rule instead of column_name.
In this PR two new types were introduced
column_name_ext which is almost as column_name but has primary DOUBLE_QUOTE_STRING rule to track double quoted column only for PostgreSQL.
column_name_expression - which is the same as value_expression but used column_name_ext instead of column_name.
This PR contains only
sqlparser
changes to fix the open issue. During debugging we faced that sqlparser flow has incorrect flow for parsing statements asWHERE "column" = 'value'
as it looks onvalue
rule instead ofcolumn_name
.In this PR two new types were introduced
column_name_ext
which is almost ascolumn_name
but has primary DOUBLE_QUOTE_STRING rule to track double quoted column only for PostgreSQL.column_name_expression
- which is the same asvalue_expression
but usedcolumn_name_ext
instead ofcolumn_name
.Checklist