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 of your target Prisma release and follow the transaction and error-mapping contract.

startTransaction acquires one dedicated connection, begins the transaction, and applies the isolation level. commit and rollback are lifecycle cleanup hooks that release the connection once, while optional createSavepoint, rollbackToSavepoint, and releaseSavepoint methods handle nested transactions on that connection.

P2039 surfaces when an unmapped driver error reaches Prisma. Preserve originalCode and originalMessage in your DriverAdapterError conversion so the fallback contains useful details, and map known conditions like unique violations to structured MappedError kinds.

No. Prisma coordinates SQL COMMIT and ROLLBACK through executeRaw. The transaction object's commit and rollback methods are lifecycle hooks that detach listeners and release the dedicated connection exactly once, never issuing duplicate SQL.

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