#26290: Pagination module should warn about unordered query set
--------------------------------------+------------------------------------
Reporter: kartikanand | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: pagination | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by jarshwah):
Hmm I don't agree Simon. There's a vast difference between not ordered and
mostly ordered. If a column is not unique you can still order by a second
clause which will get you even closer to a unique ordering (and so on).
Any duplicates in the final ordering will be randomly ordered (database
dependent), but non duplicates will still be in the correct order. For
most applications I would expect that to be OK.
Documentation should definitely be added. I would probably also like to
see a warning about a completely unordered paginated queryset for the
users sake.
--
Ticket URL: <https://code.djangoproject.com/ticket/26290#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.c5a7fc35ca589394ff7287f91f304549%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
