prisma-driver-adapter-implementation

Implement SqlDriverAdapterFactory with a connect() method returning a SqlDriverAdapter that provides queryRaw, executeRaw, executeScript, startTransaction, and dispose. Match the exact @prisma/driver-adapter-utils version installed by your target Prisma release, since the protocol boundary is version-sensitive.

startTransaction must acquire one dedicated connection, issue BEGIN, apply the isolation level, and return a Transaction bound to that connection. commit() and rollback() are lifecycle cleanup hooks only; Prisma issues the SQL COMMIT/ROLLBACK via executeRaw, and savepoints are optional methods on the Transaction object.

P2039 surfaces when an unmapped driver error reaches Prisma. Wrap recognized driver failures in DriverAdapterError and always preserve originalCode and originalMessage, even when falling back to the provider-specific raw error variant, so P2039 remains debuggable.

Only if you implement SqlMigrationAwareDriverAdapterFactory for Prisma Migrate. connectToShadowDb() must create an isolated shadow database with a cryptographically unique name, connect to it, and drop it during disposal or failure cleanup—never point it at the primary database.

Common mistakes include sharing one connection across parallel transactions, issuing duplicate SQL COMMIT/ROLLBACK inside lifecycle hooks, tracking transaction depth globally on the adapter, splitting migration scripts naively on semicolons, and disposing caller-owned connection pools.