Offset pagination becomes a stable cursor contract
For backend engineers converting a real query without skipping or duplicating rows.
Works with
- Codex
The prompt289 words · 3 blanks
What you fill in
- Current pagination code
[source_query]ExampleSQL query plus caller code using LIMIT and OFFSET - SQL dialect
[database_engine]ExamplePostgreSQL - Required ordering
[sort_contract]Examplecreated_at DESC, id DESC; new inserts may arrive between requests
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Offset pagination becomes a stable cursor contract”.
- 2Fill in the 3 blanks. current pagination code, sql dialect and required ordering — the only things the prompt cannot know.
- 3Copy and paste it into Codex. That is the tool it is written for.
About this prompt
“Offset pagination becomes a stable cursor contract” is a advanced coding prompt. For backend engineers converting a real query without skipping or duplicating rows. It is 289 words long and written to get a usable answer on the first message, in Codex or any other chat assistant. Good for: rewrite, sql, api design, performance and migration. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
