#26434: Inconsistent results of QuerySet.count() when ordering is not a subset
of
explicit grouping.
-------------------------------------+-------------------------------------
Reporter: kamandol | Owner: Michal
| Mládek
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: postgresql queryset | Triage Stage: Ready for
count annotate aggreagate | checkin
order_by |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"ea3a71c2d09f8281d8a50ed20e40e1fb13db5cd9" ea3a71c2]:
{{{#!CommitTicketReference repository=""
revision="ea3a71c2d09f8281d8a50ed20e40e1fb13db5cd9"
Fixed #26434 -- Removed faulty clearing of ordering field when missing
from explicit grouping.
Co-authored-by: Simon Charette <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26434#comment:28>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a27151262-8a58e8e1-2fd8-444d-bb2c-290861f08193-000000%40eu-central-1.amazonses.com.
