Examples

---
title: "Fix Prisma N+1 query problem with includes and joins"
slug: fix-prisma-n-plus-one-queries
tags: [prisma, database, performance, n-plus-one]
problem: "Prisma makes hundreds of individual queries when loading related data in a loop"
solution_type: fix
created: "2026-02-08"
environment:
  language: typescript
  framework: prisma
---

## Problem

Loading a list of records and then accessing their relations triggers one
additional query per record:

\`\`\`typescript
const posts = await prisma.post.findMany();
for (const post of posts) {
  const author = await prisma.user.findUnique({
    where: { id: post.authorId },
  });
}
\`\`\`

With 100 posts, this generates 101 database queries.

## Solution

**Option 1: Use `include` to eager-load relations (recommended)**

\`\`\`typescript
const posts = await prisma.post.findMany({
  include: { author: true },
});
\`\`\`

**Option 2: Use `select` for specific fields (better performance)**

\`\`\`typescript
const posts = await prisma.post.findMany({
  select: {
    id: true,
    title: true,
    author: { select: { name: true, email: true } },
  },
});
\`\`\`

**Option 3: Use `relationLoadStrategy: "join"` (Prisma 5.9+)**

\`\`\`typescript
const posts = await prisma.post.findMany({
  relationLoadStrategy: "join",
  include: { author: true },
});
\`\`\`

## Context

- Prisma 4.x+ for `include`, Prisma 5.9+ for `relationLoadStrategy: "join"`
- Use Prisma's query logging to detect N+1: `new PrismaClient({ log: ["query"] })`
- For GraphQL resolvers, consider `prisma-graphql-fields-optimizer` or DataLoader pattern
- `select` is more efficient than `include` when you don't need all columns

---
title: "Use TypeScript satisfies operator for type-safe config objects"
slug: fix-typescript-satisfies-type-safety
tags: [typescript, satisfies, type-safety, config]
problem: "Type annotation on config object widens types and loses literal inference"
solution_type: pattern
created: "2026-02-08"
environment:
  language: typescript
  version: "4.9+"
---

---
title: "fix stuff"
slug: Fix_Stuff
tags: [Fix, stuff, things, misc, general, code, programming, software, development, engineering, TypeScript]
problem: "broken"
solution_type: pattern
created: Feb 8
---

## Problem

This is a common issue that many developers face when working with
modern web frameworks. There are several approaches to solving it,
and in this share I will walk you through the best one I found after
trying many different things.

## Solution

Just add `include` to your query. This should fix it.

```
prisma.post.findMany({ include: { author: true } })
```

## Why It Works

It works because we added `include: { author: true }` to the query.
This tells Prisma to include the author in the results. See the
Prisma documentation for more information.

## Context

This solution uses Prisma's include feature to eager-load relations.
When you use include, Prisma will automatically join the related table
in the SQL query. This is much more efficient than loading each relation
individually. The include feature has been available since Prisma 2.0
and is the recommended approach for loading related data.