prisma-client-api

Use the where option with filter operators like equals, contains, in, gt, and lt, combined with logical operators AND, OR, and NOT. For example, where: { role: 'ADMIN', email: { contains: '@prisma.io' } } returns matching records.

Prisma supports sequential transactions via prisma.$transaction([op1, op2]) and interactive transactions via prisma.$transaction(async (tx) => {...}). Interactive transactions allow dependent operations and conditional logic, with options for maxWait, timeout, and isolationLevel.

select returns only the specified scalar fields, while include loads entire related records alongside all scalar fields. You cannot combine select and omit on the same query, but select and include can be nested inside relation options.

Yes, $queryRaw and $executeRaw use tagged templates that parameterize interpolated values, preventing SQL injection. Avoid $queryRawUnsafe with string concatenation of user input; use Prisma.sql, Prisma.join, and Prisma.raw for dynamic fragments.

Next.js hot reloading re-executes modules, creating a new PrismaClient on each reload and exhausting database connections. Store the client on globalThis in a singleton pattern so the instance persists across reloads in development.

Use upsert when a record may already exist and you want to update it or create it otherwise, keyed by a unique field. It takes where, update, and create arguments, avoiding separate existence checks and race conditions.