contributte / contributte/datagrid
Feature: Indeterminate paginator
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 296
- Forks
- 215
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have a huge tables (10s of millions of rows) which I use for searching in using datagrid. How ever there is an issue, COUNT for paginator is awfully slow because of how PostgreSQL works with counting.
I'd like to switch to indeterminate paginator where total count is not known and next pages is loaded based just on offset and limit and if no more rows are returned, it would be considered the end.
What do you think of such feature?
Currently there would be few issues, mainly datagrid does not allow custom paginators, and also DataModel is internal class which will call for count every time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the datagrid handles custom paginators and how the internal DataModel currently performs COUNT queries. Define the behavior for offset and limit pagination, including treating an empty result as the end, then verify the design against large PostgreSQL-backed tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100