Repository navigation
feat: support VACUUM as a no-op - #532
Merged
Merged
Conversation
Support the `VACUUM` statement as a no-op.
Codecov Report
@@ Coverage Diff @@
## postgresql-dialect #532 +/- ##
========================================================
+ Coverage 88.59% 88.62% +0.03%
- Complexity 2103 2132 +29
========================================================
Files 123 124 +1
Lines 6959 7095 +136
Branches 982 1010 +28
========================================================
+ Hits 6165 6288 +123
- Misses 562 569 +7
- Partials 232 238 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
olavloite
marked this pull request as ready for review
December 8, 2022 16:32
olavloite
requested review from
fenilfadadu,
gauravsnj,
manu2 and
pratickchokhani
December 8, 2022 16:32
pratickchokhani
approved these changes
Jan 16, 2023
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.
Support the
VACUUMstatement as a no-op. Executing aVACUUMstatement on PGAdapter is a no-operation, but it will verify that the syntax that is used is valid, and that the tables and columns that are referenced are valid and do exist.go/pgadapter-vacuum