#28705: Wrong annotation when used with QuerySet.order_by()
-------------------------------------+-------------------------------------
Reporter: Rafael Capucho | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: Annotate, ORM, | Triage Stage:
Order_by | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* component: Uncategorized => Database layer (models, ORM)
Comment:
Could you add a `tests.py` file that demonstrates the issue (and/or
replace the screenshot in the description)? The screenshot isn't
particularly friendly for someone trying to reproduce this since they have
to retype everything.
Did you read the
[https://docs.djangoproject.com/en/dev/topics/db/aggregation
/#aggregations-and-other-queryset-clauses aggregation topic guide] to
ensure that none of the documented issues there are the cause of the
behavior?
--
Ticket URL: <https://code.djangoproject.com/ticket/28705#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.7e35de0d975fb5da0f55fa3189164ca4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.