prisma-driver-adapter-implementation

Implement SqlDriverAdapterFactory, SqlDriverAdapter, and Transaction against the exact @prisma/driver-adapter-utils version of your target Prisma release. Map query arguments and result column types precisely, and follow the transaction lifecycle rules for commit, rollback, and savepoints.

startTransaction must acquire one dedicated connection, begin the transaction, apply the isolation level, and return a Transaction bound to that connection. The commit() and rollback() methods are lifecycle cleanup hooks that release the connection once; Prisma issues the actual SQL COMMIT or ROLLBACK through executeRaw.

Yes, Transaction optionally supports createSavepoint, rollbackToSavepoint, and releaseSavepoint for providers that support them. Savepoint state must live on the transaction's connection, never as adapter-global depth, and identifiers must be validated or quoted.

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

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