Repository navigation
Follow sqlparser main to a1b99f2 - #183
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sqlparser
mainnow parses a grantee written afterPUBLICinGRANTandREVOKE, andCREATE GROUP. Following it letsREVOKE ... FROM PUBLIC, anonread in the order PostgreSQL documents it, and gives the nameCREATE GROUPtakes to the role namespace, so a laterCREATE ROLEof that name is refused as the server refuses it. The pending-parser notes lose those two entries and the one for role membership, whichmainalready parses and records.This carries the part of #177 that never reached
main: #177 was merged into its stacked base after that base had landed, and the rest of it (ATTACH PARTITION) arrived through #172.