optimizing-query-selection

N+1 queries occur when you fetch a list then query each item's relations separately. Use Prisma's select or include to load relations in a single query, and apply _count to fetch relation counts without additional requests.

Include fetches all fields plus specified relations; select fetches only specified fields and relations. Select is more efficient for APIs and large datasets because it reduces data transfer and memory usage.

Use select to fetch only required fields instead of entire records, apply take to limit result set size, and nest selects for related data. This minimizes data transfer and memory consumption on large result sets.

Yes. Combine select with take and skip parameters to paginate while fetching only needed fields. Add _count to relations if you need relation counts without loading full related records.

Slow queries often result from loading unnecessary fields or relations, or querying fields without database indexes. Use select for precise field control, add indexes on filtered or ordered fields, and enable query logging to identify bottlenecks.