-
Notifications
You must be signed in to change notification settings - Fork 573
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
Fix quoted identifier regression edge-case with "from" in SELECT #1346
Fix quoted identifier regression edge-case with "from" in SELECT #1346
Conversation
Pull Request Test Coverage Report for Build 9992710189Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much @alexander-beedie
cc @MohamedAbdeen21 as the author of #1212
@alexander-beedie I don't think we are setup to make a 0.48.1
patch release at this time, but I think I could make a small 0.49.0
release.
That would be great; whatever best fits your release model is fine by me 🙂 |
Nice catch. Thanks for fixing it |
Thanks again -- I'll try and release the next version sometime this week: #1332 |
Fantastic; will finish integrating the new code on our side once it's out. |
This fix has been published as part of |
Many thanks! |
#1212 introduced a regression in the recently released 0.48, disallowing the (valid) quoted identifier
"from"
in SELECT clauses, eg:Improved the check by additionally confirming that the potentially invalid
from
is not quoted, and added coverage.FYI: this was caught by our (Polars) SQL unit tests while I was looking to upgrade us to 0.48 to take advantage of some recent PRs. Not sure if you usually make minor point releases to address regressions? If not, we can wait until 0.49 (or temporarily point to the fix on a branch), so no rush if that's the case 👍