Prisma ORM setup in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run `prisma migrate dev` without a schema file?

You run the command prisma migrate dev in your Next.js project but you forgot to create or specify a schema.prisma file. What will happen?

A Prisma throws an error saying it cannot find the schema file.

B Prisma creates a default schema file automatically and runs migration.

C The command runs but skips migration silently.

D The command runs successfully and creates an empty migration.

💡 Hint

Think about what Prisma needs to know before it can create migrations.

Prisma requires a schema.prisma file to know your database models. Without it, the migrate command cannot proceed and throws an error.

📝 Syntax

intermediate

Which Prisma schema datasource block correctly connects to a PostgreSQL database?

Choose the correct datasource block for connecting Prisma to a PostgreSQL database.

A

datasource db {
  provider = "postgresql"
  url      = "DATABASE_URL"
}

B

datasource db {
  provider = "postgres"
  url      = env("DATABASE_URL")
}

C

datasource db {
  provider = "pg"
  url      = env("DATABASE_URL")
}

D

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

💡 Hint

The provider name must match Prisma's expected string exactly.

Prisma expects the provider to be exactly "postgresql" for PostgreSQL databases. The URL should be read from environment variables using env().

❓ state_output

advanced

What is the output of this Prisma client query in Next.js?

Given the following Prisma client code in a Next.js API route, what will be the output if the database has no users?

NextJS

import { PrismaClient } from '@prisma/client';
const prisma = new PrismaClient();

export default async function handler(req, res) {
  const users = await prisma.user.findMany();
  res.json({ count: users.length, users });
}

A {"count":0,"users":[]}

B {"count":0,"users":null}

C {"count":null,"users":null}

D An error is thrown because the user table is empty.

💡 Hint

Think about what findMany() returns when no records exist.

The findMany() method returns an empty array if no records are found, so users.length is 0 and users is an empty array.

🔧 Debug

advanced

Why does this Prisma client query throw a runtime error?

Consider this Prisma client query in a Next.js app:

const user = await prisma.user.findUnique({ where: { id: 123 } });
console.log(user.name);

Why might this code throw an error?

A Because the <code>id</code> field must be a string, not a number.

B Because <code>findUnique</code> returns null if no user with id 123 exists, so accessing <code>name</code> causes a TypeError.

C Because <code>findUnique</code> requires a second argument specifying fields to select.

D Because Prisma client methods must be called inside a React component.

💡 Hint

What happens if no record matches the query?

If no user with id 123 exists, findUnique returns null. Trying to access name on null causes a runtime TypeError.

🧠 Conceptual

expert

What is the main benefit of using Prisma's generated client in a Next.js app?

Why do developers prefer using Prisma's generated client instead of writing raw SQL queries in Next.js applications?

A It automatically scales the database server based on app traffic without configuration.

B It replaces the need for a database by storing data in memory.

C It provides type-safe database queries that catch errors during development and improve code reliability.

D It allows writing SQL queries directly inside React components without any setup.

💡 Hint

Think about how Prisma helps with code safety and developer experience.

Prisma generates a client with types based on your schema, so you get autocomplete and error checking before running your app, making database access safer and easier.

Practice

1. What is the primary purpose of the schema.prisma file in a Next.js project using Prisma ORM?

easy

A. To write API routes for Next.js

B. To define the database models and their relationships

C. To configure Next.js page routing

D. To style the application components

Solution

1. Step 1: Understand the role of schema.prisma

   This file is used to define the data models and how they relate to each other in the database.

2. Step 2: Differentiate from other files in Next.js

   API routes and page routing are handled by Next.js files, not schema.prisma. Styling is done with CSS or styling libraries.

3. Final Answer:

   To define the database models and their relationships -> Option B

4. Quick Check:

   schema.prisma = data models [OK]

Hint: Remember: schema.prisma defines your database structure [OK]

Common Mistakes:

• Confusing schema.prisma with API route files
• Thinking schema.prisma handles styling
• Assuming schema.prisma manages Next.js routing

2. Which of the following is the correct way to import and instantiate the Prisma Client in a Next.js API route?

easy

A. import { PrismaClient } from '@prisma/client'; const prisma = new PrismaClient();

B. const prisma = require('@prisma/client').PrismaClient();

C. import prisma from '@prisma/client'; const client = new prisma();

D. import Prisma from 'prisma'; const prisma = Prisma.Client();

Solution

1. Step 1: Check the correct import syntax for Prisma Client

   The official way is to import PrismaClient as a named import from '@prisma/client'.

2. Step 2: Instantiate PrismaClient correctly

   Use the new keyword to create an instance: new PrismaClient().

3. Final Answer:

   import { PrismaClient } from '@prisma/client'; const prisma = new PrismaClient(); -> Option A

4. Quick Check:

   Correct import and instantiation = import { PrismaClient } from '@prisma/client'; const prisma = new PrismaClient(); [OK]

Hint: Use named import and new keyword for PrismaClient [OK]

Common Mistakes:

• Using require() instead of import
• Calling PrismaClient as a function without new
• Incorrect import paths or default imports

3. Given the following Prisma model in schema.prisma:

model Post {
  id        Int      @id @default(autoincrement())
  title     String
  published Boolean  @default(false)
}

What will be the result of this Prisma Client query?

const posts = await prisma.post.findMany({ where: { published: true } });
console.log(posts);

medium

A. A single post object with published true

B. An array of all posts regardless of published status

C. An error because 'published' is not a valid field

D. An array of posts where published is true

Solution

1. Step 1: Understand the Prisma model and query

   The model has a Boolean field published. The query filters posts where published is true.

2. Step 2: Analyze the query result

   findMany returns an array of all matching posts, so it returns all posts with published: true.

3. Final Answer:

   An array of posts where published is true -> Option D

4. Quick Check:

   findMany with where filter = array filtered by condition [OK]

Hint: findMany returns arrays filtered by where conditions [OK]

Common Mistakes:

• Expecting a single object instead of an array
• Ignoring the where filter and expecting all posts
• Thinking 'published' field does not exist

4. You wrote this code in a Next.js API route:

import { PrismaClient } from '@prisma/client';
const prisma = new PrismaClient();

export default async function handler(req, res) {
  const user = await prisma.user.findUnique({ where: { id: req.query.id } });
  res.json(user);
}

But you get an error: TypeError: Cannot read property 'id' of undefined. What is the likely cause?

medium

A. PrismaClient is not instantiated correctly

B. The findUnique method does not exist

C. The req.query object is undefined or missing id

D. You forgot to import res from Next.js

Solution

1. Step 1: Identify the error cause

   The error says Cannot read property 'id' of undefined, meaning req.query is undefined or id is missing.

2. Step 2: Check the API route usage

   Ensure the request URL includes a query parameter ?id=someValue so req.query.id exists.

3. Final Answer:

   The req.query object is undefined or missing id -> Option C

4. Quick Check:

   Missing query param causes undefined error [OK]

Hint: Check if query parameters exist before accessing them [OK]

Common Mistakes:

• Assuming PrismaClient instantiation causes this error
• Thinking findUnique method is invalid
• Trying to import res object explicitly

5. You want to add a new model Comment related to Post in your Prisma schema, where each comment belongs to one post. Which of the following schema additions correctly sets up this relationship?

hard

A. model Comment {
id Int @id @default(autoincrement())
content String
postId Int
post Post @relation(fields: [postId], references: [id])
}

model Post {
id Int @id @default(autoincrement())
title String
comments Comment[]
}

B. model Comment {
id Int @id @default(autoincrement())
content String
post Post
}

model Post {
id Int @id @default(autoincrement())
title String
}

C. model Comment {
id Int @id @default(autoincrement())
content String
postId Int
}

model Post {
id Int @id @default(autoincrement())
title String
comments Comment[]
}

D. model Comment {
id Int @id @default(autoincrement())
content String
postId Int
post Post
}

model Post {
id Int @id @default(autoincrement())
title String
comments Comment[]
}

Solution

1. Step 1: Understand Prisma relations syntax

   To relate Comment to Post, Comment needs a foreign key postId and a relation field post with @relation specifying fields and references.

2. Step 2: Check the Post model for back relation

   Post should have a comments field as an array of Comment to represent one-to-many relation.

3. Final Answer:

   Option A correctly defines the foreign key, relation, and back relation -> Option A

4. Quick Check:

   Relation fields with @relation and back array = model Comment { id Int @id @default(autoincrement()) content String postId Int post Post @relation(fields: [postId], references: [id]) } model Post { id Int @id @default(autoincrement()) title String comments Comment[] } [OK]

Hint: Use @relation with fields and references for foreign keys [OK]

Common Mistakes:

• Omitting @relation attribute causing errors
• Not defining back relation array in Post
• Missing foreign key field postId in Comment