prisma-driver-adapter-implementation

Implement SqlDriverAdapterFactory with a connect() method returning a SqlDriverAdapter that provides queryRaw, executeRaw, executeScript, and startTransaction. Match the exact @prisma/driver-adapter-utils version of your target Prisma release and follow the result and error mapping rules.

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 or ROLLBACK via executeRaw, and savepoints are optional methods on the Transaction object.

P2039 surfaces when an unmapped driver error reaches Prisma. Wrap driver failures in DriverAdapterError and always preserve originalCode and originalMessage so the fallback error remains diagnosable instead of fabricating a GenericJs id.

No. Prisma coordinates the SQL COMMIT and ROLLBACK through executeRaw. The transaction's commit() and rollback() methods are lifecycle hooks that must only detach listeners and release the dedicated connection exactly once.

Implement SqlMigrationAwareDriverAdapterFactory only when you can create an isolated shadow database, connect to it, and drop it during disposal or failure cleanup. Never point the shadow adapter at the primary database, and use quoted, cryptographically unique identifiers.