Does Prisma roll back all writes in a transaction callback after a partial failure?
Goal: Determine whether Prisma Client’s $transaction callback provides full atomicity when an error is thrown after some writes have already succeeded within the same transaction scope. Constraints: The transaction API reuses a single connection for the callback, uses SAVEPOINTs for nested writes on supported databases, and automatically rolls back on any th
prisma