prisma-driver-adapter-implementation

Implement SqlDriverAdapterFactory with a connect() method returning a SqlDriverAdapter that provides queryRaw, executeRaw, executeScript, and startTransaction. Map arguments using both value and ArgType, return column metadata in array row mode, and wrap driver failures in DriverAdapterError.

startTransaction must acquire one dedicated connection, issue BEGIN, apply the isolation level, and return a Transaction bound to that connection. commit() and rollback() are lifecycle hooks that release the connection once; Prisma issues the actual SQL COMMIT/ROLLBACK via executeRaw, and savepoints are optional methods on the Transaction.

Yes, through optional createSavepoint, rollbackToSavepoint, and releaseSavepoint methods on the Transaction object. Never track transaction depth on the shared adapter, since parallel transactions make adapter-global state incorrect.

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

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