-
Notifications
You must be signed in to change notification settings - Fork 46
Add additional set operations #25
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
Conversation
@michaelmior Thanks for this pr, but I don't want to merge this one.
In my opinion, It will be easier to maintain this repo just support mysql syntax follows official document. Source code can be readable too.
On the other hand, table join syntax can touch the aim of what INTERSECT and EXCEPT do.
No problem, I understand although I don't really see this making things less readable. Of course queries can be rewritten, but this doesn't help when I need to parse the alternative syntax. That said, I can always maintain my own fork and I appreciate having this as a starting point :)
Uh oh!
There was an error while loading. Please reload this page.
This provides a partial implementation for #18. Basically almost the same grammar is used but
INTERSECTandEXCEPTare allowed as keywords in addition toUNION. Each of these parses into a new kind of top-level expression. This is roughly following what Postgres does since these are not all supported by MySQL.