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 errors in DriverAdapterError.

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

Yes, through optional createSavepoint, rollbackToSavepoint, and releaseSavepoint methods on the Transaction object. Implement them only where the provider supports savepoints, validate identifiers, and never track nesting depth on the shared adapter.

P2039 surfaces when an unmapped driver error reaches Prisma. Preserve originalCode and originalMessage in your DriverAdapterError conversion so the fallback remains useful, and map known conditions like unique constraint violations to structured MappedError kinds.

A shadow database is an isolated database used by Prisma Migrate to validate migrations. Adapters implementing SqlMigrationAwareDriverAdapterFactory must create it with a unique quoted name, connect to it, and drop it during disposal or failure cleanup, never pointing it at the primary database.