Database integration patterns in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the database client in a Remix loader function.

Remix

import { [1] } from '~/db.server';

export async function loader() {
  const data = await [1].getData();
  return data;
}

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

AdbClient

Bjson

CuseLoaderData

DfetchData

Attempts:

3 left

💡 Hint

Common Mistakes

Using client-side hooks like useLoaderData in server code.

Importing functions that are not related to database access.

The database client is usually imported as dbClient from the server database file to access data.

2fill in blank

medium

Complete the code to create a database connection using Prisma in Remix.

Remix

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

const [1] = new PrismaClient();

export default [1];

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

Aclient

Bdb

Cdatabase

Dprisma

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic names like db or client which can be confusing.

Not exporting the Prisma client instance.

The common convention is to name the Prisma client instance prisma.

3fill in blank

hard

Fix the error in the Remix action function to insert data into the database.

Remix

import prisma from '~/db.server';

export async function action({ request }) {
  const formData = await request.formData();
  const name = formData.get('name');

  await prisma.user.[1]({ data: { name } });

  return null;
}

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

AcreateUser

Bcreate

Cinsert

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like insert or add.

Confusing method names with SQL commands.

The Prisma client uses create to add new records to the database.

4fill in blank

hard

Fill both blanks to query users with a specific email and select only their names.

Remix

const users = await prisma.user.findMany({
  where: { email: [1] },
  select: { [2]: true }
});

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

A"[e-mail]"

Bname

Cemail

D"[e-mail]"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong field name in select.

Not using quotes around the email string.

The where clause filters by email string, and select picks the name field.

5fill in blank

hard

Fill all three blanks to update a user's name by ID and return the updated record.

Remix

const updatedUser = await prisma.user.[1]({
  where: { id: [2] },
  data: { name: [3] }
});

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

Aupdate

B42

C"New Name"

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using delete instead of update.

Not quoting the new name string.

The update method changes a record by id and sets the new name.

Practice

1. In Remix, which function is primarily used to fetch data from a database before rendering a page?

easy

A. componentDidMount

B. action

C. useEffect

D. loader

Solution

1. Step 1: Understand Remix data fetching

   Remix uses loader functions to fetch data on the server before rendering.

2. Step 2: Differentiate from actions and React lifecycle

   action handles data updates, useEffect and componentDidMount are React client hooks, not Remix server loaders.

3. Final Answer:

   loader -> Option D

4. Quick Check:

   Data fetching = loader [OK]

Hint: Load data with loader, update with action [OK]

Common Mistakes:

• Confusing loader with action
• Using React hooks for server data fetching
• Thinking componentDidMount runs on server

2. Which of the following is the correct syntax to export a loader function in a Remix route module?

easy

A. export const loader = async () => { return fetchData(); }

B. function loader() { return fetchData(); } export default loader;

C. export default function loader() { return fetchData(); }

D. const loader = () => fetchData();

Solution

1. Step 1: Identify correct export style

   Remix expects named exports for loaders, commonly as async arrow functions.

2. Step 2: Check each option

   A uses default export, incorrect for Remix loaders; B declares function then exports as default, also incorrect; C exports named async arrow function, correct Remix pattern; D lacks export keyword.

3. Final Answer:

   export const loader = async () => { return fetchData(); } -> Option A

4. Quick Check:

   Named async export = export const loader = async () => { return fetchData(); } [OK]

Hint: Use named async exports for loaders in Remix [OK]

Common Mistakes:

• Using default export instead of named export
• Forgetting async keyword for async data fetching
• Not exporting the loader function

3. Given this Remix loader code snippet, what will be the returned JSON data?

export const loader = async () => {
  const users = await db.user.findMany({ where: { active: true } });
  return { users };
};

medium

A. An error because 'findMany' is not a valid method

B. An object with a key 'users' containing an array of active user records

C. A stringified JSON of users without filtering

D. An array of all users including inactive ones

Solution

1. Step 1: Understand the query filter

   The query uses where: { active: true } to get only active users.

2. Step 2: Analyze the returned data structure

   The loader returns an object with key users holding the array of filtered user records.

3. Final Answer:

   An object with a key 'users' containing an array of active user records -> Option B

4. Quick Check:

   Filtered query returns object with users array [OK]

Hint: Filters in where limit results; output matches filtered data [OK]

Common Mistakes:

• Assuming all users are returned without filter
• Confusing returned object with just array
• Thinking findMany is invalid

4. Identify the error in this Remix action function that tries to insert a new user into the database:

export const action = async ({ request }) => {
  const formData = await request.formData();
  const name = formData.get('name');
  await db.user.create({ data: { name } });
  return redirect('/users');
};

medium

A. Missing import of redirect from Remix

B. Using formData.get instead of formData.post

C. Not awaiting the redirect call

D. Incorrect method db.user.create should be db.user.insert

Solution

1. Step 1: Check Remix imports

   The redirect function must be imported from Remix to be used.

2. Step 2: Validate other code parts

   formData.get is correct to get form values; redirect is synchronous; db.user.create is valid Prisma method.

3. Final Answer:

   Missing import of redirect from Remix -> Option A

4. Quick Check:

   Always import redirect before use [OK]

Hint: Check imports for Remix helpers like redirect [OK]

Common Mistakes:

• Forgetting to import redirect
• Confusing formData methods
• Misnaming Prisma methods

5. You want to fetch a list of posts and their authors in a Remix loader using Prisma. Which pattern correctly fetches posts with author data included?

hard

A. await db.post.findMany({ select: { authorId: true } })

B. await db.post.findMany({ where: { author: true } })

C. await db.post.findMany({ include: { author: true } })

D. await db.post.findMany({ include: { authorId: true } })

Solution

1. Step 1: Understand Prisma include syntax

   To fetch related data, use include with the related model name set to true.

2. Step 2: Evaluate each option

   B correctly includes author data; A only selects authorId, not full author; C misuses where for inclusion; D tries to include a field, not a relation.

3. Final Answer:

   await db.post.findMany({ include: { author: true } }) -> Option C

4. Quick Check:

   Use include to fetch related models [OK]

Hint: Use include with relation name to fetch related data [OK]

Common Mistakes:

• Using where instead of include for relations
• Selecting foreign keys instead of related objects
• Including fields instead of relations