Fixed #36648, Refs #33772 -- Accounted for composite pks in first()/last() when aggregating. #19955
+32
−2
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.
Trac ticket number
ticket-36648
Branch description
Before,
.first()
and.last()
checked if the primary key was already in the group by for an aggregation, otherwise it threw aTypeError
. (See ticket-33772).Now, if you have a composite primary key, you can also provide each column individually in a
values()
call instead of needing to use the"pk"
syntax.Checklist
main
branch.