Why Prisma offers type-safe database access in NestJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Prisma ensure type safety in database queries?

Prisma generates types based on your database schema. What is the main benefit of this for developers?

A It automatically encrypts all database data for security.

B It prevents runtime errors by catching type mismatches during development.

C It allows writing raw SQL queries without any checks.

D It disables type checking to improve performance.

💡 Hint

Think about how knowing data types early helps avoid mistakes.

Prisma generates TypeScript types from your database schema. This means your code editor and compiler can warn you if you use wrong types before running the app. This reduces bugs and improves developer confidence.

❓ component_behavior

intermediate

What happens if you try to assign a wrong type to a Prisma query result?

Consider this NestJS code using Prisma Client: const user = await prisma.user.findUnique({ where: { id: 1 } }); What will happen if you try to assign user.name (a string) to a variable declared as a number?

NestJS

const user = await prisma.user.findUnique({ where: { id: 1 } });
const age: number = user.name;

A The code will run but user.name will be converted to a number automatically.

B The app will crash at runtime with a type error.

C Prisma will ignore the type mismatch and assign the value.

D TypeScript will show a type error during development.

💡 Hint

Think about when TypeScript checks types.

TypeScript checks types during development and compilation. Assigning a string to a number variable causes a compile-time error, preventing the code from running until fixed.

📝 Syntax

advanced

Which Prisma query correctly uses type-safe filtering for a user email?

You want to find a user by email using Prisma Client in NestJS. Which code snippet is type-safe and correct?

A const user = await prisma.user.findUnique({ where: { email: null } });

B const user = await prisma.user.findUnique({ where: { email: 12345 } });

C const user = await prisma.user.findUnique({ where: { email: '[e-mail]' } });

D const user = await prisma.user.findUnique({ where: { email: true } });

💡 Hint

Check the expected type of the email field in the schema.

The email field is a string in the database schema. Prisma enforces this type, so only a string value is accepted. Other types cause TypeScript errors.

🔧 Debug

advanced

Why does this Prisma query cause a TypeScript error?

Look at this code snippet: const posts = await prisma.post.findMany({ where: { published: 'yes' } }); Why does TypeScript show an error here?

NestJS

const posts = await prisma.post.findMany({ where: { published: 'yes' } });

A The 'published' field expects a boolean, but a string was given.

B The 'published' field does not exist in the schema.

C Prisma Client does not support findMany queries.

D The 'where' clause must be empty for findMany.

💡 Hint

Check the data type of the 'published' field in your Prisma schema.

The 'published' field is a boolean in the schema. Passing a string like 'yes' causes a type mismatch error in TypeScript.

❓ state_output

expert

What is the output type of this Prisma query in NestJS?

Given this Prisma Client query: const user = await prisma.user.findUnique({ where: { id: 5 } }); What is the type of 'user' in TypeScript?

NestJS

const user = await prisma.user.findUnique({ where: { id: 5 } });

A User | null

B null

C User

D any

💡 Hint

Consider what happens if no user with id 5 exists.

The findUnique method returns the matching record or null if none is found. Prisma types reflect this by using a union type User | null.