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.
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
Parse Postgres's LOCK TABLE statement #1614
base: main
Are you sure you want to change the base?
Parse Postgres's LOCK TABLE statement #1614
Changes from all commits
bcdc790
4b191a6
47a3e5e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
we can probably skip these changes in this PR given it's now in #1613?
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.
@iffyio oh my bad - I should have branched from the apache
main
branch instead of our fork'smain
before pushing. I'll remedy this.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.
@iffyio I tried this and it's not straightforward without storing a value on the variant the identifies the dialect that was used to parse the AST.
The following syntax would be problematic (to render, in
Display
):In PG, the
TABLE
keyword is optional. In MySQL one ofTABLE
orTABLES
is mandatory.The
Display
impl forStatement
, in theLockTable { .. }
match arm could potentially generate SQL that will not be parsable by Postgres if aTABLES
keyword is emitted.Is there precedent for choosing how to render an AST fragment using a stored value to encode the dialect (or a proxy to the dialect) that was used to parse the AST?
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.
ah yeah we could probably use an enum to represent the variants, something like?
see TableSampleKind for example