Snowflake: parse ORDER BY ALL - #2502
Open
osipovartem wants to merge 1 commit into
Open
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
1 participant
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.
ORDER BY ALLis supported by Snowflake and is already represented by the sharedOrderByKind::AllAST/parser path. This PR enables that existing capability forSnowflakeDialect.The dialect-specific regression test covers a computed select expression together with
DESC NULLS FIRST; the sharedparse_select_order_by_alltest also begins exercising Snowflake for every supported option combination.Reference: https://docs.snowflake.com/en/sql-reference/constructs/order-by
Validation:
cargo +1.95.0 fmt --all -- --checkcargo +1.95.0 test --test sqlparser_snowflake parse_order_by_allcargo +1.95.0 test --test sqlparser_common parse_select_order_by_allcargo +1.95.0 clippy --all-targets -- -D warnings