# Prisma 7.9.0 — Release & Upgrade Intelligence
- **Product:** Prisma (https://prisma.io)
- **Version:** 7.9.0
- **Released:** Jul 21, 2026
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/prisma/updates/7.9.0/

## Executive Summary (TL;DR)
Prisma 7.9.0. Source highlight: Today, we are excited to share the `7.9.0` stable release 🎉

## New Features
- Added copy actions to the Query Details view.

## Bug Fixes
- Fixed a severe TypeScript performance regression introduced in Prisma 7: restoring the `OmitOpts` generic default lets `tsc` reuse cached type instantiations again, bringing type-checking on large schemas back from minutes to seconds (#29592, from @nfl1ryxditimo12).
- The `XOR` type helper now rejects primitive values such as `data: 5`, which were previously accepted at compile time even though the runtime rejected them (#29735, from @kyungseopk1m).
- `$queryRaw` and `$executeRaw` now fail fast with a clear validation error when passed an invalid `Date`, instead of silently serializing it as `null` and corrupting the value sent to the database (#29697, from @jibin7jose).
- The generated client is no longer corrupted by a `///` documentation comment that contains a `*/` sequence; the comment terminator is now escaped when doc comments are emitted, in both the TypeScript and JavaScript generators (#29736, from @kyungseopk1m).
- Improved the runtime and TypeScript error messages shown when a driver adapter is missing from the `PrismaClient` constructor; both now include a copy-pasteable example and a link to the driver adapters docs (#29624).
- Unmapped database errors from driver adapters now surface as a user-facing `P2039` (`PrismaClientKnownRequestError`) carrying the original code and message, instead of an opaque failure, which keeps schema-drift-style problems debuggable (#29512).

## Upgrade Command
```bash
npm install --save-dev --save-exact prisma@7.9.0
```