Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade sql-parser-cst from 0.5.1 to 0.10.0 #681

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

nene
Copy link
Contributor

@nene nene commented Nov 30, 2022

This version brings BigQuery support, so I also added the new language to the dropdown in settings. Plus the syntax tree produced by sql-parser-cst has had some major changes between 0.5 and 0.8 versions.

Normally I would avoid throwing PR-s to AstExplorer for every little upgrade, but this one completely changes how table and column names are represented, making the syntax tree in 0.5 largely incompatible with the one in 0.8.

This version brings BigQuery support, so also add the new language
to the dropdown in settings.

Notably the syntax tree produced by sql-parser-cst has also had
some major changes between 0.5 and 0.8 versions.  Normally I would
avoid throwing PR-s to AstExplorer for every little upgrade,
but this one completely changes how table and column names are
represented, making the syntax tree in 0.5.x largely incompatible
with the one in 0.8.x.
This fixes a major performance problem.
@nene nene changed the title Upgrade sql-parser-cst from 0.5.1 to 0.8.1 Upgrade sql-parser-cst from 0.5.1 to 0.8.2 Dec 2, 2022
@nene nene changed the title Upgrade sql-parser-cst from 0.5.1 to 0.8.2 Upgrade sql-parser-cst from 0.5.1 to 0.9.2 Dec 14, 2022
@nene nene changed the title Upgrade sql-parser-cst from 0.5.1 to 0.9.2 Upgrade sql-parser-cst from 0.5.1 to 0.10.0 Dec 22, 2022
@vsviridov
Copy link

It's on 0.17.1 with even more dialects supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants