You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Thank you VaZark for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.
Community instructions
For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"
Reaction Guide
👍 This is something I would use
👎 This is something that would cause problems for me or Django
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.
The text was updated successfully, but these errors were encountered: