#30207: Optimise paginator for tables with massive records
-------------------------------------+-------------------------------------
Reporter: M. Javidan Darugar | Owner: M.
Type: | Javidan Darugar
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi. At this point, the issue tracker here is not the appropriate place for
this discussion.
Please see TicketClosingReasons/DontReopenTickets.
Rather, a message to the DevelopersMailingList explaining the issue and
the proposed change would be needed to progress.
A couple of points to make it easier:
* This kind of thing has come up previously: search here and the mailing
list history to find the discussions. Summarizing that history may help.
* Wrapping your suggestion in a custom paginator class and providing a
sample project, with some benchmarking data maybe, so people can explore
your solution, would be useful.
* In general, the proficiency level of contributors to the ORM is very
high. They know how databases work. Assume that.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/30207#comment:9>
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/067.3e7b82e110138d331b619bcefe0ac57b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
