refactor(sql): simplify FirstValue
/LastValue
usage
#8568
Merged
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.
During recent refactors the
FirstValue
/LastValue
have been pretty much removed from the codebase - at this point they only exist since some backends require spellingfirst
/last
asfirst_value
/last_value
when used in a window function context (other backends aliasfirst
/last
to these for nicer SQL UX).This PR:
FirstValue
/LastValue
toibis/backends/sql/rewrites.py
to treat them as SQL-specific IR.First -> FirstValue
/Last -> LastValue
window function rewrites to always apply for all SQL backends, making our compilation more uniform here.