#26434: Inconsistent results of QuerySet.count() when ordering is not a subset
of
explicit grouping.
-------------------------------------+-------------------------------------
Reporter: kamandol | Owner: Michal
| Mládek
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql queryset | Triage Stage: Accepted
count annotate aggreagate |
order_by |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Michal Mládek):
I'm not sure what is expected from me at this point - there’s no single
comment addressing the solution in PR #19524
or the question(s) I raised there. That PR was rejected without a clear
explanation what is wrong, even though the issue has now been reopened and
is being discussed again.
A previously functional but incorrect implementation was first accepted
and then reverted. The proposed fix in PR #19524
, which resolved the issue by performing an early order_by, was dismissed
in favor of the flawed implementation from PR #19519
.
Could someone please clarify what exactly was wrong with the approach in
#19524, and what I should avoid when preparing a new attempt?
--
Ticket URL: <https://code.djangoproject.com/ticket/26434#comment:35>
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/0107019a2f31c512-ddd7bc50-730e-40a8-9aa1-45a7591eb1c9-000000%40eu-central-1.amazonses.com.
