#35665: Prefetch() fails with "OrderByList" when queryset has no order_by and is
sliced
-------------------------------------+-------------------------------------
Reporter: Andrew | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: prefetch slice | Triage Stage: Accepted
order_by |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew):
Replying to [comment:2 Simon Charette]:
Yes, it returns them in database order, which is acceptable in this case.
This **actually** came up due to a Model having no {{{Meta.ordering}}},
which is our standard. All ordering must be explicit at the query level.
--
Ticket URL: <https://code.djangoproject.com/ticket/35665#comment:3>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070191448c62a1-1e2e52e6-1042-47c9-b11d-ac51fe647ef4-000000%40eu-central-1.amazonses.com.
