#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: new => closed
Comment:
In [changeset:"2ce5cb0f7a4618dfdc5f5c10e53e2e9b9543d298" 2ce5cb0f]:
{{{#!CommitTicketReference repository=""
revision="2ce5cb0f7a4618dfdc5f5c10e53e2e9b9543d298"
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:43>
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/0107019b23af1575-6d01c654-a64f-450a-be0a-0dc9ce67254d-000000%40eu-central-1.amazonses.com.
