prisma

To prevent N+1 query problems in Prisma ORM, use the include keyword or batch queries to fetch related data efficiently in a single round-trip rather than issuing separate queries per record. This skill provides patterns for structuring include operations to optimize relational data loading.

Handling Prisma error codes like P2002 and P2025 requires mapping these database constraints to application-specific errors within your repository layer. This skill provides patterns for intercepting Prisma error codes and translating unique constraint violations or record-not-found errors into safe application exceptions.

Structuring a repository layer with Prisma Client involves encapsulating complex queries within dedicated repository classes to keep your services thin and enable testing. This skill provides templates for using a central PrismaService instance to standardize database access across your Node.js backend.

Use select versus include for query optimization in Prisma when you need to limit returned fields and prevent fetching unnecessary relational data. This skill provides guidelines for applying select to shape payload types and include to manage relations, ensuring queries avoid excessive joins.

Yes, Prisma $transaction supports interactive transactions for multi-step database operations requiring atomic execution. This skill provides patterns for implementing transaction semantics, ensuring safe query execution and rollback handling when wrapping multiple database changes within a single transaction block.

To type Prisma query results with GetPayload in TypeScript, extract the return type payload generated by your specific select or include operations. This skill provides advice on using GetPayload typing alongside upsert and aggregate patterns to ensure strict type safety for analytics queries and repository method returns.