Database query optimization in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to fetch all users from the database using Remix loader.

Remix

export const loader = async () => {
  const users = await db.user.[1]();
  return { users };
};

Drag options to blanks, or click blank then click option'

Adelete

BfindFirst

CfindMany

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using findFirst fetches only one user, not all users.

Using create or delete methods are for modifying data, not fetching.

The findMany method fetches all records from the database table.

2fill in blank

medium

Complete the code to select only the 'id' and 'name' fields from users.

Remix

const users = await db.user.findMany({
  select: { [1]: true, name: true }
});

Drag options to blanks, or click blank then click option'

Aid

Bemail

Cpassword

DcreatedAt

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting email instead of id when the task asks for id.

Selecting password exposes sensitive data.

Selecting id and name fields returns only those fields for each user.

3fill in blank

hard

Fix the error in the query to filter users older than 30.

Remix

const users = await db.user.findMany({
  where: { age: { [1]: 30 } }
});

Drag options to blanks, or click blank then click option'

Agt

Blt

Cequals

Dcontains

Attempts:

3 left

💡 Hint

Common Mistakes

Using equals filters only users exactly 30 years old.

Using contains is for strings, not numbers.

The gt operator means 'greater than', so it filters users older than 30.

4fill in blank

hard

Fill both blanks to optimize the query by selecting only active users and ordering by creation date descending.

Remix

const users = await db.user.findMany({
  where: { active: [1] },
  orderBy: { createdAt: [2] }
});

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

C"desc"

D"asc"

Attempts:

3 left

💡 Hint

Common Mistakes

Using false filters inactive users.

Ordering by "asc" shows oldest users first.

Filtering by active: true selects active users. Ordering by createdAt: "desc" shows newest first.

5fill in blank

hard

Fill all three blanks to create a query that selects users with email containing 'example', limits results to 5, and skips the first 10.

Remix

const users = await db.user.findMany({
  where: { email: { [1]: "example" } },
  [2]: 5,
  [3]: 10
});

Drag options to blanks, or click blank then click option'

Acontains

Btake

Cskip

Dequals

Attempts:

3 left

💡 Hint

Common Mistakes

Using equals instead of contains filters exact matches only.

Mixing up take and skip parameters.

contains filters emails containing 'example'. take limits results to 5. skip skips first 10 records.

Practice

1. What is the main benefit of optimizing database queries in a Remix app?

easy

A. It makes the UI look better

B. It makes the app faster and reduces server load

C. It increases the size of the database

D. It adds more data to the database

Solution

1. Step 1: Understand query optimization purpose

   Optimizing queries means making them run faster and use fewer resources.

2. Step 2: Connect optimization to app performance

   Faster queries reduce server load and improve user experience by loading data quickly.

3. Final Answer:

   It makes the app faster and reduces server load -> Option B

4. Quick Check:

   Optimization = faster app and less server load [OK]

Hint: Optimization means faster queries and less server work [OK]

Common Mistakes:

• Thinking optimization adds more data
• Confusing UI appearance with query speed
• Believing optimization increases database size

2. Which of the following is the correct way to limit results in a Remix loader using Prisma?

easy

A. const users = await prisma.user.findMany({ max: 10 });

B. const users = await prisma.user.findMany({ limit: 10 });

C. const users = await prisma.user.findMany({ take: 10 });

D. const users = await prisma.user.findMany({ count: 10 });

Solution

1. Step 1: Recall Prisma syntax for limiting results

   Prisma uses the 'take' option to limit the number of records returned.

2. Step 2: Identify correct option

   Only const users = await prisma.user.findMany({ take: 10 }); uses 'take: 10', which is the correct syntax.

3. Final Answer:

   const users = await prisma.user.findMany({ take: 10 }); -> Option C

4. Quick Check:

   Use 'take' to limit results in Prisma [OK]

Hint: Use 'take' to limit records in Prisma queries [OK]

Common Mistakes:

• Using 'limit' instead of 'take' in Prisma
• Using 'max' or 'count' which are invalid options
• Confusing SQL syntax with Prisma syntax

3. Given this Remix loader code using Prisma:

const posts = await prisma.post.findMany({ where: { published: true }, orderBy: { createdAt: 'desc' }, take: 5 });

What will be the result?

medium

A. Throws a syntax error due to orderBy usage

B. Returns all posts regardless of published status

C. Returns 5 oldest posts including unpublished

D. Returns the 5 most recent published posts

Solution

1. Step 1: Analyze the filter condition

   The 'where' clause filters posts to only those with 'published: true'.

2. Step 2: Understand sorting and limiting

   'orderBy: { createdAt: "desc" }' sorts posts newest first, and 'take: 5' limits to 5 posts.

3. Final Answer:

   Returns the 5 most recent published posts -> Option D

4. Quick Check:

   Filter + sort + limit = 5 newest published posts [OK]

Hint: Filter first, then sort descending, then limit [OK]

Common Mistakes:

• Ignoring the 'where' filter and returning all posts
• Thinking 'orderBy' sorts ascending by default
• Assuming syntax error with 'orderBy' in Prisma

4. You wrote this Prisma query in a Remix loader:

const users = await prisma.user.findMany({ where: { age: { gt: 18 } }, limit: 10 });

But it throws an error. What is the problem?

medium

A. The 'limit' option is invalid in Prisma queries

B. The 'gt' operator is not supported

C. Missing 'orderBy' clause causes error

D. The 'where' clause syntax is incorrect

Solution

1. Step 1: Check Prisma query options

   Prisma uses 'take' to limit results, not 'limit'. Using 'limit' causes an error.

2. Step 2: Confirm other parts are correct

   'gt' is valid for greater than, and 'where' syntax is correct.

3. Final Answer:

   The 'limit' option is invalid in Prisma queries -> Option A

4. Quick Check:

   Use 'take' not 'limit' in Prisma [OK]

Hint: Replace 'limit' with 'take' in Prisma queries [OK]

Common Mistakes:

• Using 'limit' instead of 'take'
• Thinking 'gt' is invalid
• Assuming missing 'orderBy' causes error

5. You want to optimize a Remix loader that fetches posts with their authors but only needs the post title and author name. Which Prisma query is best for performance?

hard

A. await prisma.post.findMany({ select: { title: true, author: { select: { name: true } } } });

B. await prisma.post.findMany({ include: { author: true } });

C. await prisma.post.findMany();

D. await prisma.post.findMany({ where: { title: { not: null } } });

Solution

1. Step 1: Understand data needed

   Only post titles and author names are needed, so selecting only those fields reduces data load.

2. Step 2: Compare query options

   await prisma.post.findMany({ select: { title: true, author: { select: { name: true } } } }); uses 'select' to fetch only required fields, improving performance. await prisma.post.findMany({ include: { author: true } }); fetches full author data, await prisma.post.findMany(); fetches all post fields, and await prisma.post.findMany({ where: { title: { not: null } } }); filters but does not limit fields.

3. Final Answer:

   await prisma.post.findMany({ select: { title: true, author: { select: { name: true } } } }); -> Option A

4. Quick Check:

   Select only needed fields for best performance [OK]

Hint: Use 'select' to fetch only needed fields [OK]

Common Mistakes:

• Using 'include' fetches all author fields unnecessarily
• Fetching all fields wastes resources
• Filtering without selecting fields doesn't optimize data size