Skip to content

Conversation

@BentiGorlich
Copy link
Member

@BentiGorlich BentiGorlich commented Jan 31, 2026

  • instead of the usual LIMIT/OFFSET pagination use cursor based one based on the current ordering
  • Write classes that are inspired by the pagination of doctrine for cursor based pagination
  • make the ContentRepository work with the new pagination, while still working with the regular one

Left ToDos:

  • API
  • Infinite Scroll support
  • RSS

Fixes #1869

@BentiGorlich BentiGorlich self-assigned this Jan 31, 2026
@BentiGorlich BentiGorlich added backend Backend related issues and pull requests performance This is a issue regarding performance. labels Jan 31, 2026
@BentiGorlich BentiGorlich modified the milestone: v1.10.0 Feb 4, 2026
- instead of the usual `LIMIT`/`OFFSET` pagination use cursor based one based on the current ordering
- Write classes that are inspired by the pagination of doctrine for cursor based pagination
- make the `ContentRepository` work with the new pagination, while still working with the regular one
- add API endpoint to retrieve content using the cursor pagination
- add tests for the `CombinedRetrieveApi`
- make `CombinedRetrieveApi` actually returning combined content
@BentiGorlich BentiGorlich force-pushed the new/front-cursor-pagination branch from 1069a55 to fe09af6 Compare February 4, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend Backend related issues and pull requests performance This is a issue regarding performance.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Peformance: Threads (+ Microblog) frontpage query

2 participants