Tim

The generated parser.c got too large (about 83MB)

6

Hi fellows, I am making contribution to the [tree-sitter-sql repo](https://github.com/m-novikov/tree-sitter-sql). As commits are added, it takes longer and longer to generate the parser (about 42s on [the latest commit](https://github.com/m-novikov/tree-sitter-sql/commits/ff7a41074022bf48b2319990d48e5d02fe569cc0)), and...

Generated too large parser.c ~ 83M

7

With all PRs merged, tree-sitter will generate a very large parser.c file (about 83M). And it takes about 1 min to load the parser by tree-sitter python binding. Unfortunately I...

Improve from clause

2

Improved the FROM clause in SELECT statement to make it more general, ref: https://www.postgresql.org/docs/current/sql-select.html#SQL-FROM

To avoid potential name collision, this PR renamed the alias name `default` to `default_value`

Supported the DO statement for PostgreSQL. Ref: https://www.postgresql.org/docs/current/sql-do.html

Supported the VACUUM statement and improved the alias rule. Ref: https://www.postgresql.org/docs/current/sql-vacuum.html

Supported combining queries, JSON comparison operators and type cast as column default. Ref: * https://www.postgresql.org/docs/current/queries-union.html * https://www.postgresql.org/docs/current/functions-json.html

Supported composite values of the form: ~~~ (expression1, expression2, ...) ~~~ as an expression, and resolved the syntax conflicts. The conflict is explained at https://www.postgresql.org/docs/current/queries-table-expressions.html#QUERIES-GROUPING-SETS as following >Note The construct...

Support more comparison predicates: 1. BETWEEN...AND expression; 2. ISNULL and NOTNULL; 3. IS UNKNOWN and IS NOT UNKNOWN; Ref: https://www.postgresql.org/docs/current/functions-comparison.html

Some more improvements: - Fully support TRUNCATE statement; - Supported DISTINCT clause in SELECT statement; - Improved the IN expression to support select-subexpression;