CRUD with Prisma in NestJS - Step-by-Step Execution

Concept Flow - CRUD with Prisma

Start CRUD Operation

↓

Receive Request

↓

Call Prisma Client Method

↓

Database Executes Query

↓

Return Result to Controller

↓

Send Response to Client

↓

End

This flow shows how a CRUD operation with Prisma in NestJS starts from a request, calls Prisma methods to interact with the database, and returns the result back to the client.

Execution Sample

NestJS

async createUser(data) {
  return await this.prisma.user.create({ data });
}

This code creates a new user record in the database using Prisma's create method.

Execution Table

Step	Action	Prisma Method Called	Input Data	Database Result	Response Sent
1	Receive create user request	N/A	{ name: 'Alice', email: '[e-mail]' }	N/A	N/A
2	Call prisma.user.create	create	{ name: 'Alice', email: '[e-mail]' }	User record created with id 1	N/A
3	Database executes insert query	N/A	N/A	Inserted user with id 1	N/A
4	Return created user object	N/A	N/A	{ id: 1, name: 'Alice', email: '[e-mail]' }	N/A
5	Send response to client	N/A	N/A	N/A	{ id: 1, name: 'Alice', email: '[e-mail]' }

💡 Request completed after sending created user data as response

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
data	undefined	{ name: 'Alice', email: '[e-mail]' }	{ name: 'Alice', email: '[e-mail]' }	{ name: 'Alice', email: '[e-mail]' }	N/A
result	undefined	undefined	{ id: 1, name: 'Alice', email: '[e-mail]' }	{ id: 1, name: 'Alice', email: '[e-mail]' }	{ id: 1, name: 'Alice', email: '[e-mail]' }

Key Moments - 3 Insights

Why do we await the prisma.user.create call?

Because prisma.user.create returns a promise that resolves when the database operation finishes. Awaiting it ensures we get the created user data before continuing, as shown in execution_table step 2.

What happens if the input data is missing required fields?

Prisma will throw an error during the database query (step 3), and the request will fail before sending a response (step 5). This is why validation before calling Prisma is important.

Is the database query synchronous or asynchronous?

It is asynchronous. The code waits for the database to finish (step 3) before returning the result (step 4), which is why async/await is used.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'result' after step 2?

A undefined

B User record created with id 1

C N/A

D Inserted user with id 1

💡 Hint

Check the 'Response Sent' column at step 2 in the execution_table.

At which step does the database actually insert the new user?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the step mentioning 'Database executes insert query' in the execution_table.

If the input data was missing the email, what would likely happen?

A Prisma would throw an error during the database query

B The request would succeed but return empty data

C The user would be created with a null email

D The response would be sent before database insertion

💡 Hint

Refer to the key_moments about missing required fields and errors.

Concept Snapshot

CRUD with Prisma in NestJS:
- Use async methods like prisma.model.create(data)
- Await promises to get results
- Input data must match schema
- Prisma sends queries to DB asynchronously
- Return DB results to client
- Handle errors for missing or invalid data

Full Transcript

This visual execution trace shows how a create operation works with Prisma in a NestJS app. First, the app receives a request with user data. Then it calls prisma.user.create with that data and awaits the result. The database inserts the new user record asynchronously. Once done, Prisma returns the created user object. Finally, the app sends this user data back to the client as a response. Variables like input data and result change step-by-step. Key points include awaiting Prisma calls to handle async DB operations and validating input to avoid errors. The quiz questions help check understanding of these steps.