Repository navigation
Fix CTE recognition after INSERT columns and preserve enclosing indentation - #414
Merged
Merged
Conversation
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.
I ran into a couple of indentation problems with CTEs after an
INSERTcolumn list: sibling CTEs become progressively indented, and queries inside a PL/pgSQL block can jump back to column zero. This keeps the CTEs and their final query at the enclosing block’s indentation level.Before (
pg_format, default options):After (
pg_format, default options):Two existing expected-output files also contained examples of queries losing their enclosing indentation. Their changes reflect the same fix.
I ran
prove -l t/and the larger SQL corpus withperl t/regress_test.pl; both pass. The focused cases also produce the same output when formatted twice.Thanks for taking a look!