[Solved] A developer wrote this query for keyset pagination:SELECT * FROM messages WHERE timestamp > :last_timestamp ORDER BY timestamp DESC LIMIT 20;What is the issue with this query? | Rest API

Rest API - Pagination Patterns

A developer wrote this query for keyset pagination:

SELECT * FROM messages WHERE timestamp > :last_timestamp ORDER BY timestamp DESC LIMIT 20;

What is the issue with this query?

AUsing timestamp instead of id is invalid

BOrdering DESC with > operator causes missing rows

CLIMIT 20 is too large for keyset pagination

DNo WHERE clause to filter rows

Step-by-Step Solution

Solution:

Step 1: Check ordering and filter logic
Ordering DESC means newest first, but WHERE timestamp > last_timestamp fetches newer timestamps, which conflicts.
Step 2: Understand keyset pagination consistency
For DESC order, filter should be WHERE timestamp < last_timestamp to get older rows.
Final Answer:
Ordering DESC with > operator causes missing rows -> Option B
Quick Check:
Order and filter mismatch = C [OK]

Quick Trick: Match WHERE operator direction with ORDER BY [OK]

Common Mistakes:

Master "Pagination Patterns" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

A developer wrote this query for keyset pagination: