Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#14942 closed (invalid)

.distinct() + ordering/order_by() is a problem even without related models

Reported by: Christophe Pettus Owned by: nobody
Component: Documentation Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


The documentation at implies that using .distinct() with ordering (which can come from either the Meta value or the .order_by() call on the QuerySet) is only an issue if you are querying across related models, but that's not true; it can bite you even if you are staying within the same model. A rewrite of the note in question is probably in order.

Change History (3)

comment:1 Changed 6 years ago by Gabriel Hurley

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset

Can you provide an example of when/why this is can be a problem when ordering with fields on a single model?

comment:2 Changed 6 years ago by Russell Keith-Magee

Resolution: invalid
Status: newclosed

Closing invalid; the report asserts that the problem exists on single-model queries, but doesn't elaborate on the circumstances in which it is a problem, and it's not obvious to me (or Gabriel, obviously) what the problem case would be.

Feel free to reopen if you can provide more details (either draft replacement text, or a simple example of a problem case)

comment:3 Changed 5 years ago by Jacob

milestone: 1.3

Milestone 1.3 deleted

Note: See TracTickets for help on using tickets.
Back to Top