#35452: Unexpected results when Paginator's orphans is equal or higher than the
page size
-------------------------------------+-------------------------------------
Reporter: Strapchay | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: pagination, | Triage Stage: Accepted
paginator |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Strapchay):
I do not have a specific use case for having an orphan greater than the
page size. I was only trying to get the results needed from a test case
and needed the data gotten back to not break the ui context of amount to
fit into the screen and created a base test case which was how I noticed
the issue in the first place. I think the first one would be great. Also
why not have a warning or an exception raised when the orphan specified is
more than the page_size?, or what's your thought on that?
--
Ticket URL: <https://code.djangoproject.com/ticket/35452#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/0107018f7f3077d7-62334128-90c3-4255-af27-bfb857cf10a3-000000%40eu-central-1.amazonses.com.
