#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: | no | UI/UX: | no |
Description
The documentation at http://docs.djangoproject.com/en/1.2/ref/models/querysets/#distinct 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 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
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)
Can you provide an example of when/why this is can be a problem when ordering with fields on a single model?