Repository navigation
Format SQL-like input tolerantly and correct block layout - #3
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.
changes
), next as (and plain integer TOP counts-StrictThe fallback preserves unfamiliar syntax rather than translating dialects. It preserves inline spacing, organizes recognizable boundaries, and returns unchanged input with a warning if it cannot retain the tokens. File/dependency/output failures remain errors. No database execution or claim of PostgreSQL/MySQL validation.
checks
The published 2.27.0 installation is unchanged. The 2.28.0 candidate is for review.
refs #2