-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support for distinct
in functions and between
#22
Comments
Hi there @sebastian, sorry for the late reply. It has been a busy and hectic start of a year 😅
My pleasure 😄 I really appreciate the support ❤️ 🙏
PRs are always welcome! I can't think of anything special to consider, really. I think only the fact that the parser as a standalone thing needs to be published separately which is something I have to do at some point. Additions to the parser would be great as long as the tests keep passing 😉 |
Absolutely no problems with the late reply. I imagined you had plenty to do. |
Glad you have found a workaround. It might be for the better because this parser really is extremely limited and works only in combination with metadata from the database.
Don't worry about it at all, if you don't need it now then just forget about 😉 if you still want the parser as a standalone library, ping me here and I will publish it 😄 |
Then I'll forget about it for now, and look for time to make some more meaningful contribution in some other projects of yours down the line instead. |
Dear @Zaid-Ajaj, thank you for all the wonderful work you are doing for the open-source community!
I am considering using the SQL parser part of your library in a reference implementation I am building.
Currently, it is missing two features I would rely on, namely:
distinct
keyword in a function (such ascount(distinct column)
, andBETWEEN
keyword forWHERE
-clauses (WHERE age BETWEEN 1 and 20
)Would you welcome pull-requests to add these features?
If yes, are there any particular things I should keep in mind while adding these features? Say some non-obvious aspect of your library that doesn't immediately spring to mind but needs to be considered?
The text was updated successfully, but these errors were encountered: