-
-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve some DB expression types #1243
Conversation
Sorry, lots of conflicts here due to #1253 I promise I will review this if you resolve the conflicts. :) |
5239987
to
5cee9ec
Compare
Rebased! Tests failed due to an apt issue, fix in #1313. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one import can be cleaned up.
self, | ||
expression: Expression | F | Subquery, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reordering the classes here made it very difficult to understand what actually changed here. I had to order them back to get a readable diff.
In the future, if you want to reorder items, please do it as a separate PR without any additional changes.
I have made things!
GeoAggregate
andGeoFuncMixin
where the inherited types are correct**extra_context
toFunc.as_sql
Agggregate.as_sql
since it’s a pass-through toFunc.as_sql
db/models/expressions.pyi
to follow the same order as upstreamDurationExpression
,TemporalSubtraction
,Star
, andOrderByList
Related issues
n/a
Spotted the problem with
Aggregate
when adding Mypy to Django-MySQL, which has a custom aggregate class.