Offset Pagination & Count Metadata Implement numbered pages with skip/take and truthful totals
Phase 15 - Filtering, Search, Sorting & Pagination Volume 04 - Professional Backend
page/pageSize
v
skip/take
v
findMany + count
v
data + meta
Phase 15 turns an unbounded collection endpoint into a validated, queryable, stable, paginated API contract.
Offset pagination is the first TaskFlow implementation Offset pagination maps naturally to numbered pages. Prisma expresses it with skip and take. The SQL concept is OFFSET/LIMIT. This is easy to understand and fits administrative tables where users expect page numbers and direct page navigation.
const skip = (query.page - 1) * query.pageSize;const items = await prisma.task.findMany({ where, orderBy, skip, take: query.pageSize, });
page pageSize skip rows requested
The deep-page trade-off Offset pagination becomes more expensive as the offset grows because the database still has to advance past earlier rows. That does not make offset pagination wrong; it means you should use it where numbered navigation matters and dataset depth is reasonable, then measure real performance.
Count the same filtered set For numbered pages, the UI often wants totalItems and totalPages. The count query must use the same where filter as the page query. If the filters differ, the metadata lies.
const [items, totalItems] = await prisma.$transaction([ prisma.task.findMany({ where, orderBy, skip, take: pageSize }), prisma.task.count({ where }), ]);
Why group page + count?
This groups the two related reads into one database transaction call and keeps their query intent together. It does not mean every read-only list endpoint always requires a transaction; it is one practical way to execute related operations together in this course.
Offset Pagination and Count Metadata matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Offset Pagination and Count Metadata” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: query parameters → validated filter/sort → stable query → page/cursor → response metadata. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Task list API with filter/search/sort/page contract plus metadata and indexes justified by measured query patterns.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: limit + 1,
where: cursor ? {
OR: [
{ createdAt: { lt: cursor.createdAt } },
{ createdAt: cursor.createdAt, id: { lt: cursor.id } },
],
} : undefinedDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Offset Pagination and Count Metadata” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Inspect representative query plans/index needs rather than indexing every field.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Nondeterministic order causing duplicates/missing rows
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.