Create Persistent Tasks

Create Persistent Tasks POST /tasks from HTTP request to PostgreSQL INSERT

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

Architecture milestone POST /tasks

↓

Project relation check

↓

prisma.task.create()

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

POST /tasks - create the first durable Task Creation is the first operation that proves NestJS can transform an HTTP request into a persistent PostgreSQL row.

Figure 1 - Create lifecycle POST /tasks

↓

TasksController.create()

↓

TasksService.create()

↓

verify Project exists

↓

prisma.task.create()

↓

PostgreSQL INSERT

↓

201 response

The service checks parent semantics before it asks Prisma to create the Task.

Controller route @Post() create(@Body() body: CreateTaskInput) { return this.tasksService.create(body); }

NestJS uses 201 Created for a successful POST handler by default. The controller does not construct SQL and does not instantiate PrismaClient.

Service create method

async create(input: CreateTaskInput) {
const project = await this.prisma.project.findUnique({
where: { id: input.projectId },
select: { id: true },
});

if (!project) { throw new NotFoundException( `Project ${input.projectId} was not found.`, ); }

return this.prisma.task.create({ data: { projectId: input.projectId, title: input.title, description: input.description, }, }); }

Test from PowerShell From any PowerShell terminal while the API is running:

$projectId = "<PROJECT-ID-FROM-SEED>"

$body = @{ projectId = $projectId title = "Persist my first Task" description = "Created in Phase 11" } | ConvertTo-Json

$created = Invoke-RestMethod ` -Method Post ` -Uri "http://127.0.0.1:4000/tasks" ` -ContentType "application/json" ` -Body $body

$created

Checkpoint C

The response should contain a generated Task id, your projectId/title, status TODO, priority MEDIUM, and timestamps. Copy the Task id for later steps.

What the defaults teach The HTTP request did not send status, priority, id, createdAt, or updatedAt. Those values come from the Prisma/database model. Defaults are part of the durable domain contract, not UI convenience.

Known gap

Sending a missing or malformed title is not handled professionally yet. TypeScript request types vanish at runtime. Phase 12 adds real validation at the API boundary.