prisma-driver-adapter-implementation

To implement a Prisma v7 SQL driver adapter, you must build SqlDriverAdapter and SqlMigrationAwareDriverAdapterFactory implementations that adhere to Prisma's query, execute, and transaction lifecycle contracts for your target database. You map arguments and rows to typed values.

The correct transaction lifecycle for Prisma driver adapters treats commit() and rollback() as lifecycle hooks only, meaning they must not directly issue SQL. Prisma sends the necessary transaction control SQL via the executeRaw method instead.

Prisma driver adapter error handling requires wrapping database errors in DriverAdapterError with appropriate MappedError kinds, while type mapping converts database arguments to db-types and query rows back to typed values according to Prisma's strict contracts.

Yes, you can use a Prisma driver adapter with SQL Server or SQLite. The skill provides functional requirements and an implementation checklist for argument mapping, isolation-level validation, and error mapping across MySQL, PostgreSQL, SQLite, and SQL Server.

A Prisma driver adapter transaction commit fails if you issue SQL directly inside the commit() hook. Commit and rollback are lifecycle hooks only; Prisma handles transaction SQL via executeRaw, so direct SQL calls violate the adapter contract.

Yes, you need a SqlMigrationAwareDriverAdapterFactory for Prisma driver adapters when adding database drivers or touching adapter interfaces. It ensures the adapter correctly handles migration contexts alongside standard query and transaction execution.