PrismaTaskRepository: Query and Mapping Implementation Volume 07 - Advanced Application Architecture | Phase 24
Persistence details belong here The implementation owns Prisma relation filters, ordering, select/include decisions, error-code translation that is truly persistence-specific, and mapping from generated records into stable repository result shapes.
Scoped list example async listScoped( userId: string, query: TaskListQuery, ): Promise<PaginatedTasks> { const where = this.buildScopedWhere(userId, query) const orderBy = this.buildOrderBy(query) const skip = (query.page - 1) * query.pageSize
const [rows, totalItems] = await this.prisma.$transaction([ this.prisma.task.findMany({ where, orderBy, skip, take: query.pageSize, select: taskListSelect, }), this.prisma.task.count({ where }), ])
return mapPage(rows, totalItems, query) }
Why this is useful • The service no longer knows Prisma relation syntax.
• The count and data query cannot accidentally build different filters.
• Sorting allow-lists stay close to persistence mapping.
• Changing select/include structure does not force business-service edits.
Do not hide everything A repository should hide persistence mechanics that the service should not care about. It should not hide important business decisions by burying them in database code.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Prismataskrepository Query and Mapping Implementation” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. 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: One TaskFlow aggregate/use case refactored behind a purposeful repository interface with real database integration tests.. 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.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do 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.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Prismataskrepository Query and Mapping Implementation” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Decide whether persistence types may cross the boundary or need mapping and document the trade-off.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Mapping everything into duplicate types without a domain need
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.