Description
Code of Conduct
- I agree to follow Django's Code of Conduct
Feature Description
Offer a KeysetPagination with just the next and previous buttons, and fetch the items count on ajax button click (or just hide it) for the admin list view
This also helps ensure that links shared to look up a table are far more precise, as data can change between pages on a fast-moving dataset. There are some tables that I look up via a DB tool like DBeaver due to incessant http timeouts.
Problem
When working with large datasets, the admin's standard LIMIT..OFFSET pagination becomes expensive, real fast. Simple page loads can take seconds if not minutes. Add in the default count on every list page, the two queries might be too much to handle.
Request or proposal
proposal
Additional Details
No response
Implementation Suggestions
Django already offers a custom pagination class. This would essentially be leveraging the same but as an officially supported lookup method.
Metadata
Metadata
Assignees
Type
Projects
Status