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' } } filters by multiple conditions.

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

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

Yes, use $queryRaw for SELECT queries with typed results and $executeRaw for INSERT, UPDATE, or DELETE returning affected counts. Template literals parameterize values automatically; avoid $queryRawUnsafe with concatenated user input to prevent SQL injection.

Combine take, skip, and cursor with orderBy on a unique field. Fetch the first page with take: 10, then pass cursor: { id: lastId } with skip: 1 to retrieve the next page without offset scanning.

Use findUniqueOrThrow when a missing record is an error condition, since it throws PrismaClientKnownRequestError instead of returning null. This is especially useful inside interactive transactions where the throw triggers an automatic rollback.