Paginated Query Design
Lets say you have a table of messages, and you have two views in your app: Inbox and Archived.
What is the best way to design pagination queries for these two views that optimizes caching and is responsive to messages ingressing and egressing these states?
1) two separate query functions with fixed filters
2) one query with an arg to denote which messages we are currently interested in
3) doesnt matter
4) something else entirely
What is the best way to design pagination queries for these two views that optimizes caching and is responsive to messages ingressing and egressing these states?
1) two separate query functions with fixed filters
2) one query with an arg to denote which messages we are currently interested in
3) doesnt matter
4) something else entirely
