Transaction boundary issues when mixing Prisma and raw SQL

6/10 Medium

Combining Prisma Client calls with `$queryRaw` within `$transaction` blocks causes unexpected transaction boundary behavior, requiring developers to choose one approach per transaction.

Prisma
Category
compatibility
Workaround
solid
Stage
debug
Freshness
persistent
Scope
single_lib
Recurring
No
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Prisma for developers in 2025?”4/4/2026

Mixing Prisma `$transaction` with raw SQL — Transaction boundaries behave unexpectedly when combining Prisma client calls with `$queryRaw`. Stick to one approach per transaction.

Created: 4/4/2026Updated: 4/4/2026