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 lifecycle rules.

startTransaction must acquire one dedicated connection, begin the transaction, and apply the isolation level. commit() and rollback() are lifecycle cleanup hooks only; Prisma issues the SQL COMMIT/ROLLBACK itself. Savepoint methods live on the Transaction object, never as adapter-global depth.

Yes, through optional createSavepoint, rollbackToSavepoint, and releaseSavepoint methods on the Transaction interface. Implement them only where the database provider supports savepoints, and validate or quote savepoint identifiers.

P2039 surfaces when an unmapped driver error reaches Prisma. Wrap known database errors in DriverAdapterError with mapped kinds, and always preserve originalCode and originalMessage so the P2039 fallback remains useful.

A shadow database is an isolated database created by connectToShadowDb() for migration validation. It must use cryptographically unique quoted names, never point at the primary database, and be dropped during disposal or failure cleanup.