prisma-client-api

Use findMany with a where clause for filters and include or select for relations. Filter operators like equals, contains, in, gt, and logical AND/OR/NOT combine conditions, while relation filters some, every, and none match related records.

Use prisma.$transaction with an array for sequential independent operations, or pass an async function for interactive transactions where later operations depend on earlier results. Interactive transactions accept maxWait, timeout, and isolationLevel options.

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

Create an adapter such as PrismaPg with your connection string and pass it to new PrismaClient({ adapter }). For development, use a global singleton pattern to prevent multiple instances during hot reloading in frameworks like Next.js.

select returns only specified fields, include adds related records to the result, and omit excludes specific fields like passwords. You cannot combine select and omit in the same query, but include can be nested inside select.

Use findUniqueOrThrow when a missing record is an error condition, such as inside transactions where the thrown PrismaClientKnownRequestError triggers a rollback. findUnique returns null and suits cases where absence is acceptable.