prisma-driver-adapter-implementation

Implements Prisma ORM 7 SQL driver adapters with transaction, savepoint, and error-mapping contracts.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/Rithika135/watchtower-360 --skill prisma-driver-adapter-implementation-rithika135
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-driver-adapter-implementation
Source: https://github.com/Rithika135/watchtower-360/tree/main/watchtower360-backend/.windsurf/skills/prisma-driver-adapter-implementation
Command: npx skills add https://github.com/Rithika135/watchtower-360 --skill prisma-driver-adapter-implementation-rithika135

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @prisma/driver-adapter-utils.

What problem does it solve? Building a Prisma SQL driver adapter is error-prone: type-compatible code can still corrupt values, leak connections, break transactions, or lose original database error details. This Skill provides the exact contract, priority rules, and verification checklist needed to implement adapters that behave correctly under Prisma ORM 7. ## Core Features & Use Cases - Adapter Contract Implementation: Guides implementation of SqlDriverAdapterFactory, SqlDriverAdapter, Transaction, and migration-aware shadow database factories. - Transaction & Savepoint Protocol: Enforces one dedicated connection per transaction, lifecycle-only commit/rollback hooks, and connection-local savepoint handling. - Result & Error Mapping: Covers column type mapping, argument binding, and DriverAdapterError conversion that preserves original database codes for useful P2039 errors. - Use Case: You are writing a new database driver adapter for Prisma 7 and need to ensure nested transactions, shadow databases for Migrate, and constraint error mapping all pass Prisma Client integration tests. ## Quick Start Ask the AI to implement a Prisma driver adapter for your database following this guide, including transaction lifecycle, savepoints, and error mapping.

Frequently Asked Questions about prisma-driver-adapter-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a Prisma driver adapter for a new database?

Implement SqlDriverAdapterFactory with a connect() method returning a SqlDriverAdapter that provides queryRaw, executeRaw, executeScript, and startTransaction. Match the exact @prisma/driver-adapter-utils version of your target Prisma release and map arguments, column types, and errors precisely.

How do Prisma driver adapter transactions and savepoints work?

startTransaction must acquire one dedicated connection, begin the transaction, and apply the isolation level. The commit() and rollback() methods are lifecycle cleanup hooks only; Prisma issues the actual SQL COMMIT/ROLLBACK via executeRaw, and savepoints live on the Transaction object, not adapter-global state.

Why does Prisma throw P2039 with my custom driver adapter?

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

Does a Prisma driver adapter need shadow database support?

Only if you implement SqlMigrationAwareDriverAdapterFactory for Prisma Migrate. Its connectToShadowDb() must create an isolated shadow database with a unique quoted name, never point at the primary database, and clean it up on disposal or failure.

What are common mistakes when writing a Prisma driver adapter?

Common mistakes include sharing connections across concurrent transactions, issuing duplicate COMMIT/ROLLBACK in lifecycle hooks, splitting migration scripts naively on semicolons, truncating 64-bit integers into JS numbers, and disposing caller-owned connection pools.