-
Notifications
You must be signed in to change notification settings - Fork 475
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
Enable SQL features selectively #1201
Comments
I agree this is interesting, though I am not sure how easy it would be to add to the current crate |
Setting the granularity at the keyword level, maybe we can try to modify the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
given the breadth of the parser, it would be nice if it would be possible to selectively enable features on an opt-in basis.
Let's imagine an application where only a subset of SQL is supported. In this case, the application would need to check for every possible unsupported feature manually (e.g. if I don't support windowing in queries, I would need to check if the
named_window
field in theSelect
gets populated and abort).It would be interesting, instead, to decide beforehand which feature set is to be supported, so that only "valid" SQL gets parsed and arrives to the application.
Thanks.
The text was updated successfully, but these errors were encountered: