Why Prisma offers type-safe database access in NestJS - See It in Action

Why Prisma offers type-safe database access

📖 Scenario: You are building a simple NestJS backend that connects to a database using Prisma. You want to see how Prisma helps you write code that is safe and avoids mistakes by using types.

🎯 Goal: Build a small NestJS service that uses Prisma Client to fetch users from the database with type safety.

📋 What You'll Learn

Create a Prisma Client instance

Define a configuration variable for the user ID to fetch

Write a function that fetches a user by ID using Prisma Client

Return the fetched user in the service method

💡 Why This Matters

🌍 Real World

Backend developers use Prisma with NestJS to safely query databases without runtime errors from wrong field names or types.

💼 Career

Understanding Prisma's type-safe access helps developers write reliable, maintainable backend code that integrates well with TypeScript and NestJS.

1

Create Prisma Client instance

Create a constant called prisma and set it to a new instance of PrismaClient imported from @prisma/client.

NestJS

# Your code here

Hint

Use import { PrismaClient } from '@prisma/client' and then const prisma = new PrismaClient().

2

Add user ID configuration

Create a constant called userId and set it to the number 1 to represent the user ID you want to fetch.

NestJS

import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

# Your code here

Hint

Just create const userId = 1.

3

Write function to fetch user by ID

Write an async function called getUserById that takes a parameter id of type number. Inside, use prisma.user.findUnique with where: { id } to fetch the user. Return the result.

NestJS

import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

const userId = 1;

# Your code here

Hint

Use async function getUserById(id: number) and inside return await prisma.user.findUnique({ where: { id } }).

4

Call function and export result

Create an async function called main that calls getUserById with userId and stores the result in user. Export main as the default export.

NestJS

import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

const userId = 1;

async function getUserById(id: number) {
  return await prisma.user.findUnique({
    where: { id }
  });
}

# Your code here

Hint

Define async function main(), call getUserById(userId), store in user, then return user. Export main as default.

Practice

1. Why does Prisma provide type-safe database access in NestJS applications?

easy

A. To replace the need for SQL queries entirely

B. To make the database run faster

C. To automatically create database backups

D. To catch errors early by matching queries to the database schema

Solution

1. Step 1: Understand Prisma's purpose

   Prisma checks that your code queries match the database structure to avoid mistakes.

2. Step 2: Identify the benefit of type safety

   This early error detection helps developers write safer and more reliable code.

3. Final Answer:

   To catch errors early by matching queries to the database schema -> Option D

4. Quick Check:

   Type safety = early error detection [OK]

Hint: Type safety means catching mistakes before running code [OK]

Common Mistakes:

• Thinking Prisma speeds up the database itself
• Confusing type safety with backups
• Believing Prisma removes all SQL usage

2. Which of the following is the correct way to import Prisma Client in a NestJS service for type-safe access?

easy

A. const { Prisma } = require('@prisma/client');

B. import { PrismaClient } from '@prisma/client';

C. import Prisma from 'prisma';

D. const PrismaClient = require('prisma-client');

Solution

1. Step 1: Check official Prisma import syntax

   Prisma Client is imported using ES module syntax: import { PrismaClient } from '@prisma/client';

2. Step 2: Identify incorrect options

   Options A, B, and C use wrong module names or CommonJS require syntax not recommended in NestJS with ES modules.

3. Final Answer:

   import { PrismaClient } from '@prisma/client'; -> Option B

4. Quick Check:

   Correct import syntax = import { PrismaClient } from '@prisma/client'; [OK]

Hint: Use ES module import syntax for Prisma Client [OK]

Common Mistakes:

• Using require() instead of import
• Wrong package names like 'prisma-client'
• Destructuring Prisma instead of PrismaClient

3. Given this Prisma query in a NestJS service:

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

What will happen if the id field does not exist in the database schema?

medium

A. The query will run but return null

B. The database will ignore the id filter

C. TypeScript will show a compile-time error

D. The application will crash at runtime

Solution

1. Step 1: Understand Prisma's type safety

   Prisma generates types from the database schema, so invalid fields cause TypeScript errors before running.

2. Step 2: Identify error timing

   Since id is missing, TypeScript will catch this mismatch during compilation, preventing runtime errors.

3. Final Answer:

   TypeScript will show a compile-time error -> Option C

4. Quick Check:

   Invalid field = compile-time error [OK]

Hint: Prisma type safety catches wrong fields before running code [OK]

Common Mistakes:

• Assuming runtime crash instead of compile error
• Thinking database ignores unknown fields silently
• Believing query returns null without error

4. You wrote this Prisma query in NestJS:

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

But you get a TypeScript error: Property 'title' does not exist on type 'PostWhereInput'.
What is the most likely cause?

medium

A. The title field is missing in the Prisma schema for Post

B. You forgot to import PrismaClient

C. The database connection is not established

D. You used findMany instead of findUnique

Solution

1. Step 1: Analyze the TypeScript error

   The error says title is not a valid filter field, meaning it is not defined in the Prisma schema for Post.

2. Step 2: Rule out other options

   Missing import or connection issues cause different errors; findMany is valid here.

3. Final Answer:

   The title field is missing in the Prisma schema for Post -> Option A

4. Quick Check:

   Missing schema field = TypeScript error [OK]

Hint: Check Prisma schema fields if TypeScript errors on filters [OK]

Common Mistakes:

• Blaming database connection for type errors
• Confusing method names causing this error
• Ignoring schema updates after changes

5. In a NestJS app using Prisma, you want to ensure your database queries are type-safe and reflect the latest schema changes. Which approach best achieves this?

hard

A. Run prisma generate after updating the Prisma schema file

B. Manually write TypeScript types for your database models

C. Use raw SQL queries inside Prisma without type checks

D. Disable type checking in your IDE

Solution

1. Step 1: Understand Prisma's code generation

   Running prisma generate updates the generated client with types matching the current schema.

2. Step 2: Evaluate other options

   Manual types risk errors; raw SQL skips type safety; disabling checks removes benefits.

3. Final Answer:

   Run prisma generate after updating the Prisma schema file -> Option A

4. Quick Check:

   Generate client = updated type safety [OK]

Hint: Always run prisma generate after schema changes [OK]

Common Mistakes:

• Writing manual types instead of generating
• Ignoring schema updates in code
• Disabling helpful type checks