#26290: Pagination module should warn about unordered query set
--------------------------------------+------------------------
Reporter: kartikanand | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords: pagination
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------
Let's say somebody is using Gunicorn with more than one worker process.
Let's say contact_list is the following: (Paginating by 3)
{{{
[123, 456, 789, 345, 567, 909, 102]
}}}
When the first worker process handles request for page 1, it is possible
that it gets the first three
{{{
[123, 456, 789],
}}}
but when the second worker process handles the request for page 2, it is
very much possible that it returns,
{{{
[456, 789, 345]
}}}
See the duplicate results above. This is because the query set is
'''unordered'''.
The above "may" also happen with just one worker process.
The documentation should warn about inconsistent pagination when no
ordering is specified.
--
Ticket URL: <https://code.djangoproject.com/ticket/26290>
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/054.d7f13e890961c99f3273a86c5986407b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
