Skip to content

WIP: fetch only one page in DB when paginating, not entire list#472

Open
sypets wants to merge 1 commit intomainfrom
paginate-fetch-only-one-page-in-db
Open

WIP: fetch only one page in DB when paginating, not entire list#472
sypets wants to merge 1 commit intomainfrom
paginate-fetch-only-one-page-in-db

Conversation

@sypets
Copy link
Owner

@sypets sypets commented Feb 8, 2026

todo (functionality)

  • requires to replace array chunking (of list of pages to avoid limits in DB because of possible "too many placeholders in prepared statement), e.g. use temporary table
  • requires to change DB query
  • requires to change pagination, we currently use core functionality which requires to fetch entire list and then paginate

additional todo:

  • create issue / issues

motivation

  • performance
  • use less memory (out of memory possible)
  • "cleaner" / better solutions

@sypets sypets self-assigned this Feb 8, 2026
@sypets sypets force-pushed the paginate-fetch-only-one-page-in-db branch from 9fc43ee to 6493319 Compare February 10, 2026 10:34
@sypets sypets force-pushed the paginate-fetch-only-one-page-in-db branch from 6493319 to d4b18fa Compare February 14, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant