prisma-driver-adapter-implementation

Implement SqlDriverAdapterFactory with a connect method returning a SqlDriverAdapter that provides queryRaw, executeRaw, executeScript, startTransaction, and dispose. Typecheck against the exact @prisma/driver-adapter-utils version installed by the target Prisma release.

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, not SQL COMMIT or ROLLBACK issuers.

Yes, Transaction optionally supports createSavepoint, rollbackToSavepoint, and releaseSavepoint methods. Implement them only where the provider supports savepoints, validate identifiers, and keep nested state on the transaction connection rather than adapter-global depth.

P2039 surfaces when an unmapped driver error reaches Prisma. Preserve originalCode and originalMessage in your DriverAdapterError conversion so the fallback remains 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.