#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 charettes):
If we were to document or raise a warning in this case it must also be
done when a queryset is ordered but not by any unique expression.
Else I don't see much benefit as ordering by a non unique expression can
lead to the same undefined ordering reported here.
Since I can't think of any reliable way of determining if a queryset is
uniquely ordered (matching ordered fields against `unique` and
`unique_together` can yields false positive as users might have defined
unique functional indexes using `RunSQL`) I think we should favor a
documentation patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/26290#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.87105c43b1cdec684dbafa6f73a33986%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
