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

Only if you want Prisma Migrate support. Implement SqlMigrationAwareDriverAdapterFactory with connectToShadowDb() that creates an isolated shadow database, connects to it, and drops it during disposal or failure cleanup, never pointing it at the primary database.

Common mistakes include sharing connections across parallel transactions, issuing duplicate SQL COMMIT/ROLLBACK in lifecycle hooks, splitting migration scripts naively on semicolons, truncating 64-bit integers, and replacing all unknown errors with fabricated GenericJs ids instead of rethrowing genuine programming bugs.