Repository navigation
Conversation
This commit changes none handling at the output of pipe operators to drop singlton nones. If a none is created the query writer knows what they are doing, and if they didn't want to drop it, they should use ??. We also changed the behavior of pipe expression subqueries to return none instead of null for empty result. SQL subqueries still return null.
Collaborator
Author
|
Gonna work on this some ore |
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.
This commit changes none handling at the output of pipe operators to drop singlton nones. If a none is created the query writer knows what they are doing, and if they didn't want to drop it, they should use ??. We also changed the behavior of pipe expression subqueries to return none instead of null for empty result. SQL subqueries still return null.