prisma-driver-adapter-implementation

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

startTransaction must acquire one dedicated connection, begin the transaction, and apply the isolation level. 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.

No. Prisma coordinates the SQL COMMIT and ROLLBACK through executeRaw. The transaction's commit() and rollback() methods only detach listeners and release the dedicated connection exactly once, never issuing a second SQL commit or rollback.

P2039 surfaces when an unmapped driver error reaches Prisma. Preserve originalCode and originalMessage in your DriverAdapterError mapping so P2039 carries useful details, and rethrow genuinely unexpected non-driver errors instead of fabricating GenericJs ids.

Common mistakes include sharing connections across parallel transactions, keeping savepoint depth on the shared adapter, splitting migration scripts naively on semicolons, truncating 64-bit integers, and disposing caller-owned pools. The verification checklist covers each of these cases.