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 contracts.

startTransaction acquires one dedicated connection, issues BEGIN, applies the isolation level, and returns a Transaction bound to that connection. commit and rollback are lifecycle cleanup hooks only, while optional createSavepoint, rollbackToSavepoint, and releaseSavepoint methods handle nested transactions.

Yes, by implementing SqlMigrationAwareDriverAdapterFactory with connectToShadowDb, which must 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.

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

Common mistakes include sharing connections across concurrent transactions, issuing duplicate SQL COMMIT or ROLLBACK in lifecycle hooks, tracking savepoint depth globally on the adapter, splitting scripts naively on semicolons, and truncating 64-bit integers during result mapping.