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 map arguments, column types, and errors precisely.

startTransaction must acquire one dedicated connection, begin the transaction, and apply the isolation level. commit() and rollback() are lifecycle cleanup hooks that release the connection once; Prisma issues the actual SQL COMMIT/ROLLBACK via executeRaw. Savepoint methods are optional and live on the Transaction object.

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

Yes, implement SqlMigrationAwareDriverAdapterFactory with connectToShadowDb() when the provider can create an isolated shadow database. The shadow database must be uniquely named, never point at the primary database, and be dropped during disposal or failure cleanup.

Common mistakes include sharing connections across concurrent transactions, issuing duplicate SQL COMMIT/ROLLBACK inside lifecycle hooks, tracking transaction depth globally on the adapter, splitting migration scripts naively on semicolons, and losing 64-bit integer precision during result mapping.