prisma-driver-adapter-implementation

Implement four layers: a SqlQueryable base class with queryRaw and executeRaw, a Transaction class with commit and rollback hooks, a SqlDriverAdapter adding executeScript and startTransaction, and a SqlMigrationAwareDriverAdapterFactory exposing connect and connectToShadowDb.

commit() and rollback() are lifecycle hooks only and must not issue SQL, because Prisma sends COMMIT and ROLLBACK via executeRaw. startTransaction issues BEGIN at depth one and SAVEPOINT sp_N for nested transactions.

Yes, startTransaction accepts an IsolationLevel, but the adapter must validate it per database. PostgreSQL supports all standard levels, SQLite only supports SERIALIZABLE, and invalid levels must throw DriverAdapterError with kind InvalidIsolationLevel.

Catch driver errors and rethrow them as DriverAdapterError wrapping a MappedError. Map database-specific codes, such as PostgreSQL 23505 to UniqueConstraintViolation, or use the postgres or sqlite error kinds with code and message fields.

Arguments need string-to-int, string-to-bigint, string-to-float, and base64-to-bytes conversion. Result rows need bigint-to-string, Date-to-ISO-string, and JSON-to-string mapping, with column types reported via ColumnTypeEnum.