n-plus-one-prevention

To fix N+1 queries in your ORM, you enforce eager loading to fetch related data in a single query. This Skill specifies detection patterns and safe fallback strategies to replace per-item queries with bulk or joined fetches.

The best way to prevent N+1 queries in a list endpoint is to refactor loops that fetch related data into a single, joined or bulk-loaded query path, enforcing eager loading across your ORM framework.

You refactor a loop to use eager loading by replacing per-item database queries with a single bulk or joined query. This turns a two-step process, like fetching orders then customers, into one optimized query path.

Yes, this N+1 prevention approach works with Prisma and TypeORM. It provides eager loading guidance and detection patterns that apply across popular ORM frameworks to optimize data access.

You need to apply N+1 query prevention strategies when you have list endpoints or loops that fetch related data across an ORM. If your code executes separate queries for each item to get related data, N+1 prevention is required.