Prisma ORM with GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Prisma ORM in the context of GraphQL?

Prisma ORM is a tool that helps you talk to your database easily. It creates a simple way to read and write data, which works well with GraphQL servers to fetch or change data.

beginner

How does Prisma help when building a GraphQL API?

Prisma acts like a bridge between your GraphQL API and the database. It lets you write simple code to get or save data without writing complex database queries.

intermediate

What is a Prisma Client?

Prisma Client is an auto-generated library that lets your code talk to the database. You use it inside your GraphQL resolvers to fetch or update data easily.

intermediate

Why use Prisma schema in a GraphQL project?

The Prisma schema defines your database models and how they relate. It helps Prisma generate the client and keeps your database structure clear and synced with your GraphQL API.

intermediate

How do GraphQL resolvers use Prisma Client?

Resolvers call Prisma Client methods to get or change data. For example, a resolver for a query might use Prisma to find records in the database and return them to the user.

What does Prisma ORM primarily do in a GraphQL setup?

A Connects GraphQL queries to the database easily

B Creates GraphQL schemas automatically

C Replaces GraphQL resolvers

D Manages frontend UI components

Prisma ORM helps connect your GraphQL queries and mutations to the database by providing an easy-to-use client.

What is generated from the Prisma schema file?

A Database UI

B GraphQL schema

C Prisma Client library

D Frontend code

The Prisma schema file is used to generate the Prisma Client, which is a library to interact with the database.

In GraphQL, where do you typically use Prisma Client?

A Inside resolvers to fetch or update data

B In the frontend components

C To define GraphQL types

D To style the UI

Prisma Client is used inside GraphQL resolvers to perform database operations.

Which language is Prisma schema written in?

A SQL

B Prisma schema language

C JavaScript

D GraphQL SDL

Prisma schema uses its own schema language to define models and relations.

What is a benefit of using Prisma with GraphQL?

A Manages server hosting

B Automatically creates frontend UI

C Replaces the need for GraphQL queries

D Simplifies database access and reduces errors

Prisma simplifies database access and helps avoid common errors by providing a typed client.

Explain how Prisma ORM integrates with a GraphQL API to handle data.

Think about how data flows from GraphQL queries to the database.

Describe the role of Prisma Client in a GraphQL resolver function.

Focus on what happens inside the resolver when a query or mutation runs.

Practice

1. What is the main role of Prisma ORM when used with GraphQL?

easy

A. To define GraphQL schema types

B. To style the frontend user interface

C. To handle HTTP requests from clients

D. To manage database access and queries easily

Solution

1. Step 1: Understand Prisma ORM's purpose

   Prisma ORM acts as a tool to simplify database operations by providing an easy way to query and manage data.

2. Step 2: Differentiate Prisma from GraphQL schema and frontend roles

   GraphQL schema defines data types and operations, while frontend styling is unrelated to Prisma's role.

3. Final Answer:

   To manage database access and queries easily -> Option D

4. Quick Check:

   Prisma ORM = database access tool [OK]

Hint: Prisma handles database, GraphQL defines schema [OK]

Common Mistakes:

• Confusing Prisma with GraphQL schema definition
• Thinking Prisma manages frontend UI
• Assuming Prisma handles HTTP requests

2. Which of the following is the correct way to import Prisma Client in a Node.js GraphQL resolver file?

easy

A. import Prisma from 'prisma';

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

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

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

Solution

1. Step 1: Recall Prisma Client import syntax

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

2. Step 2: Identify incorrect import forms

   Options B, C, and D use wrong package names or destructuring that Prisma does not support.

3. Final Answer:

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

4. Quick Check:

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

Hint: Use exact package '@prisma/client' with named import [OK]

Common Mistakes:

• Using wrong package name like 'prisma-client'
• Incorrect destructuring of PrismaClient
• Mixing CommonJS require with ES import incorrectly

3. Given this GraphQL resolver using Prisma:

const users = await prisma.user.findMany({ where: { active: true } });
return users;

What does this resolver return?

medium

A. All users including inactive ones

B. Only users with active set to true

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

D. An empty list always

Solution

1. Step 1: Analyze the Prisma query filter

   The query uses findMany with a where clause filtering users where active equals true.

2. Step 2: Understand the result of the query

   It returns only users whose active field is true, excluding inactive users.

3. Final Answer:

   Only users with active set to true -> Option B

4. Quick Check:

   findMany with where active:true = filtered users [OK]

Hint: Where filters results; active:true returns only active users [OK]

Common Mistakes:

• Assuming it returns all users ignoring filter
• Thinking it causes an error without schema check
• Believing it always returns empty list

4. You wrote this resolver code but get an error:

const newUser = prisma.user.create({
  data: {
    name: 'Alice'
  }
});
return newUser;

What is the likely cause of the error?

medium

A. Missing await before prisma.user.create call

B. Incorrect field name 'name' in data

C. Using create instead of findMany

D. Returning newUser before defining it

Solution

1. Step 1: Check asynchronous Prisma call

   prisma.user.create returns a Promise, so it needs await to resolve before returning.

2. Step 2: Identify missing await causing error

   Without await, newUser is a Promise, not the created user object, causing issues in return.

3. Final Answer:

   Missing await before prisma.user.create call -> Option A

4. Quick Check:

   Async Prisma calls need await [OK]

Hint: Always await Prisma async calls in resolvers [OK]

Common Mistakes:

• Forgetting to await async Prisma methods
• Assuming create returns data synchronously
• Confusing create with findMany usage

5. You want to fetch a user and their posts in one GraphQL query using Prisma. Which resolver code correctly fetches the user with their posts included?

hard

A. const user = await prisma.user.findUnique({ where: { id }, include: { posts: true } });

B. const user = await prisma.user.findMany({ where: { id }, select: { posts: false } });

C. const user = await prisma.post.findMany({ where: { userId: id } });

D. const user = await prisma.user.findUnique({ where: { id } }); const posts = await prisma.post.findMany({ where: { userId: id } });

Solution

1. Step 1: Understand Prisma's include option

   Using include: { posts: true } fetches related posts along with the user in one query.

2. Step 2: Compare options for fetching user with posts

   const user = await prisma.user.findUnique({ where: { id }, include: { posts: true } }); uses findUnique with include correctly; const user = await prisma.user.findMany({ where: { id }, select: { posts: false } }); excludes posts; const user = await prisma.post.findMany({ where: { userId: id } }); fetches posts only; const user = await prisma.user.findUnique({ where: { id } }); const posts = await prisma.post.findMany({ where: { userId: id } }); fetches separately, not in one query.

3. Final Answer:

   const user = await prisma.user.findUnique({ where: { id }, include: { posts: true } }); -> Option A

4. Quick Check:

   Include fetches relations in one query [OK]

Hint: Use include to fetch related data in one Prisma query [OK]

Common Mistakes:

• Using findMany instead of findUnique for single user
• Not using include to fetch related posts
• Fetching posts separately causing extra queries