Read Persistent Tasks

Read Persistent Tasks Collection and detail queries with meaningful not-found behavior

Phase 11 - Persistent Task CRUD API Volume 03 - Database Engineering

Architecture milestone GET /tasks

↓

Prisma findMany/findUnique

↓

200 or 404

Phase 11 replaces process memory with durable PostgreSQL-backed application behavior.

GET /tasks - list durable rows A read operation should not know whether the row was created five seconds ago or before the API restarted. That is exactly what durable storage gives us.

findAll() { return this.prisma.task.findMany({ orderBy: { createdAt: "desc" }, }); }

This phase keeps list behavior deliberately small. Filtering, search, sorting policy, and pagination become a dedicated professional API topic in Phase 15.

Controller list route @Get() findAll() { return this.tasksService.findAll(); }

Test the collection Invoke-RestMethod ` -Method Get ` -Uri "http://127.0.0.1:4000/tasks"

GET /tasks/:id - one resource findUnique() may return null. HTTP clients should not have to understand Prisma nullability, so the service translates absence into an HTTP-aware application error.

async findOne(id: string) {
const task = await this.prisma.task.findUnique({
where: { id },
});

if (!task) { throw new NotFoundException( `Task ${id} was not found.`, ); }

return task; }

@Get(":id") findOne(@Param("id") id: string) { return this.tasksService.findOne(id); }

PowerShell detail test $taskId = "<TASK-ID>" Invoke-RestMethod ` -Method Get ` -Uri "http://127.0.0.1:4000/tasks/$taskId"

Missing resource semantics

Requesting a random Task id should return 404 Not Found. That is an API contract decision. Clients should not receive a raw Prisma error or a false 200 response with null.

Figure 1 - Read decision GET /tasks/:id

↓

findUnique(id)

↓

row exists?

↓

yes -> 200 Task | no -> 404

The service translates storage results into application semantics.