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 admins with matching emails.

Use prisma.$transaction with an array for sequential independent operations, or pass an async function for interactive transactions with dependent logic. Interactive transactions support options like maxWait, timeout, and isolationLevel such as Serializable.

select returns only the specified scalar fields, while include adds full related records to the result. Both support nesting for relations, and you cannot combine select with omit on the same query.

Yes, $queryRaw and $executeRaw use tagged templates that parameterize values automatically, preventing SQL injection. Avoid $queryRawUnsafe with string concatenation, and use Prisma.sql and Prisma.join for dynamic query fragments.

Use take and skip for offset pagination, or cursor with take for cursor-based pagination. For cursor pagination, pass the last record's unique field as cursor and set skip: 1 to exclude the cursor record itself.

Relation filters require the correct operator for the relation type: some, every, or none for to-many relations, and is or isNot for one-to-one relations. Using a to-many operator on a singular relation causes a validation error.