Implement HAVING MIN/MAX and RESPECT/IGNORE NULLS#154
Merged
makenowjust merged 6 commits intocloudspannerecosystem:mainfrom Oct 20, 2024
Merged
Conversation
makenowjust
approved these changes
Oct 20, 2024
Co-authored-by: Hiroya Fujinami <make.just.on@gmail.com>
Contributor
Author
|
Conflict resolved and suggestion applied. |
Collaborator
|
@apstndb Thank you! |
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 PR implements the current aggregate function call syntax.
https://cloud.google.com/spanner/docs/reference/standard-sql/aggregate-function-calls#aggregate_function_call_syntax
Note
NullHandlingModifierandHavingModifierare borrowed from ZetaSQLCOUNT(*)doesn't support these modifiers, soCountStarExpris not updated.fix #88