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

Yes, through SqlMigrationAwareDriverAdapterFactory, which adds connectToShadowDb. Implement it only when you can create an isolated shadow database with a unique quoted name and drop it during disposal or failure cleanup, never pointing it at the primary database.

P2039 surfaces when an unmapped driver error reaches Prisma. Preserve originalCode and originalMessage in your DriverAdapterError conversion so the fallback is useful, map known conditions to structured MappedError kinds, and rethrow genuinely unexpected non-driver errors.

Common mistakes include misaligned columnNames, columnTypes, and rows arrays, truncating 64-bit integers into JS numbers, and splitting migration scripts on semicolons. Execute queries in array row mode and use the driver's native multi-statement facility or a real SQL parser.