Prisma
✓ VerifiedGitHubNext-generation Node.js and TypeScript ORM for PostgreSQL, MySQL, SQLite, and more.
Releases
106.19.3
3 days ago
Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the effect dependency to resolve a security vulnerability.
Changes: https://github.com/prisma/prisma/pull/29416
7.6.0
1 week ago
Today, we are excited to share the 7.6.0 stable release 🎉
🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
ORM
Features
CLI
- Added a
prisma postgres linkcommand that connects a local project to a Prisma Postgres database. This is the first command in a newprisma postgrescommand group for managing Prisma Postgres databases directly from the CLI. (#29352)
Driver Adapters
- @prisma/adapter-pg: Added a
statementNameGeneratoroption that accepts a custom prepared statement name generator to allow users to leveragepgstatement caching (#29395) - @prisma/adapter-pg: Added support for usage of connection strings directly in the constructor for improved ergonomics (#29287)
- @prisma/adapter-mariadb: Added a
useTextProtocoloption in the constructor to toggle between text and binary protocols (#29392)
Bug Fixes
Prisma Client
- Disabled caching of
createManyqueries to avoid cache bloat and potential Node.js crashes in bulk operations (#29382) - Made
NowGeneratorlazy to avoid synchronousnew Date()calls, fixing Next.js "dynamic usage" errors in cached components (#28724) - Fixed missing export of
Get<Model>GroupByPayloadtype in the newprisma-clientgenerator, making it accessible for TypeScript usage (#29346)
CLI
- Added streaming parsing with automatic fallback to handle Prisma schemas that produce extremely large intermediate strings (>500MB) that hit V8's string limits (#29377)
Driver Adapters
- @prisma/adapter-pg: Relaxed the
@types/pgversion constraint to^8.16.0for compatibility with newer PostgreSQL type definitions (#29390) - @prisma/adapter-pg: Corrected error handling for
ColumnNotFounderrors to correctly extract column names from both quoted and unquoted PostgreSQL error messages (#29307) - @prisma/adapter-mariadb: Modified the adapter to disable
mariadbstatement caching by default to address a reported leak (#29392)
Prisma Studio
We’re continuing our work to improve Prisma Studio with more features being added.
Dark Mode
Need we say more? You’ve all asked for it, and it’s back.
https://github.com/user-attachments/assets/214149dd-5dd3-4295-9fa3-0da3f8d28197
Copy as markdown
Now, you can copy one or more rows as either CSV or Markdown
<img width="1888" height="672" alt="CleanShot 2026-03-11 at 16 04 09@2x" src="https://github.com/user-attachments/assets/402b4c77-08ac-4c2d-b61a-0135eb42a9af" />Multi-cell editing
This is big one, something that folks have been asking for. Now, it’s possible to edit multiple cells while inspecting your database. If you make any changes, you’ll be prompted to either save or discard them. This makes manually adding new rows much easier to accomplish.
Back relations
If your data references another table, Prisma Studio now links to the related records, making it easy to inspect them. This makes traversing your database much simpler.
https://github.com/user-attachments/assets/4977a926-413b-495f-b651-b7554eefea04
Generative SQL with AI
If you need to inspect your database, instead of manually writing the SQL you may need, you can use natural language and AI to generate the appropriate SQL statements.
https://github.com/user-attachments/assets/e57c0afb-c3ed-471b-b55a-42395a134863
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
7.5.0
3 weeks ago
Today, we are excited to share the 7.5.0 stable release 🎉
🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
ORM
Features
-
Added support for nested transaction rollbacks via savepoints (#21678)
Adds support for nested transaction rollback behavior for SQL databases: if an outer transaction fails, the inner nested transaction is rolled back as well. Implements this by tracking transaction ID + nesting depth so Prisma can reuse an existing open transaction in the underlying engine, and it also enables using
$transactionfrom an interactive transaction client.
Bug fixes
Driver Adapters
- Made the
adapter-mariadbuse the binary MySQL protocol to fix an issue with lossy number conversions (#29285) - Made
@types/pga direct dependency ofadapter-pgfor better TypeScript experience out-of-the-box (#29277)
Prisma Client
- Resolved
Prisma.DbNullserializing as empty object in some bundled environments like Next.js (#29286) - Fixed DateTime fields returning
Invalid Datewithunixepoch-mstimestamps in some cases (#29274) - Fixed a cursor-based pagination issue with
@db.Datecolumns (#29327)
Schema Engine
- Manual partial indexes are now preserved when
partialIndexespreview feature is disabled, preventing unnecessary drops and additions in migrations (#5790, #5795) - Enhanced partial index predicate comparison to handle quoted vs unquoted identifiers correctly, eliminating needless recreate cycles (#5788)
- Excluded partial unique indexes from DMMF
uniqueFieldsanduniqueIndexesto prevent incorrectfindUniqueinput type generation (#5792)
Studio
With the launch of Prisma ORM v7, we also introduced a rebuilt version of Prisma Studio. With the feedback we’ve gathered since the release, we’ve added some high requested features to help make Studio a better experience.
Multi-cell Selection & Full Table Search
This release brings the ability to select multiple cells when viewing your database. In addition to being able to select multiple cells, you can also search across your database. You can search for a specific table or for specific cells within that table.
More intuitive filtering
Filtering is now easier to use, and includes an option for raw SQL filters.
And if you are using Studio in Console, you can use ai generated filters:
Cmd+k Command Palette
You can now use the keyboard to perform most actions in Studio with the new cmd+k command palette
Run raw SQL queries
Another feature we’ve included in Prisma Studio is the ability to run raw SQL queries against your data. There’s a new “SQL” tab in the sidebar that will bring you to page where you can perform any queries against your data. Below, we’re getting all the rows in the “Todo” table.
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
7.4.2
1 month ago
Today, we are issuing a 7.4.2 patch release focused on bug fixes and quality improvements.
🛠 Fixes
Prisma Client
- Fix a case-insensitive
INandNOT INfilter regression (https://github.com/prisma/prisma/pull/29243) - Fix a query plan mutation issue that resulted in broken cursor queries (https://github.com/prisma/prisma/pull/29262)
- Fix an array parameter wrapping issue in push operations (https://github.com/prisma/prisma-engines/pull/5784)
- Fix
Uint8Arrayserialization in nested JSON fields (https://github.com/prisma/prisma/pull/29268) - Fix an issue with MySQL joins that relied on non-strict equality (https://github.com/prisma/prisma/pull/29251)
Driver Adapters
- @prisma/adapter-mariadb: Update text column detection to check for a binary collation (https://github.com/prisma/prisma/pull/29238)
- @prisma/adapter-mariadb: Correct
relationJoinscompatibility check for MariaDB 8.x versions (https://github.com/prisma/prisma/pull/29246)
Schema Engine
- Fix partial index predicate comparison on PostgreSQL and MSSQL (https://github.com/prisma/prisma-engines/pull/5780)
🙏 Huge thanks to our community
Many of the fixes in this release were contributed by our amazing community members. We're grateful for your continued support and contributions that help make Prisma better for everyone!
7.4.1
1 month ago
Today, we are issuing a 7.4.1 patch release focused on bug fixes and quality improvements.
🛠 Fixes
Prisma Client
- Fix cursor-based pagination regression with parameterised values (https://github.com/prisma/prisma/pull/29184)
- Preserve
Prisma.skipthrough query extension argument cloning (https://github.com/prisma/prisma/pull/29198) - Enable batching of multiple queries inside interactive transactions (https://github.com/prisma/prisma/pull/25571)
- Add missing JSON value deserialization for JSONB parameter fields (https://github.com/prisma/prisma/pull/29182)
- Apply result extensions correctly for nested and fluent relations (https://github.com/prisma/prisma/pull/29218)
- Allow missing config datasource URL and validate only when needed (https://github.com/prisma/prisma-engines/pull/5777)
Driver Adapters
- @prisma/adapter-ppg: Handle null values in type parsers for nullable columns (https://github.com/prisma/prisma/pull/29192)
Prisma Schema Language
- Support
whereargument on field-level@uniquefor partial indexes (https://github.com/prisma/prisma-engines/pull/5774) - Add object expression and object member support to schema reformatter (https://github.com/prisma/prisma-engines/pull/5776)
🙏 Huge thanks to our community
Many of the fixes in this release were contributed by our amazing community members. We're grateful for your continued support and contributions that help make Prisma better for everyone!
7.4.0
1 month ago
Today, we are excited to share the 7.4.0 stable release 🎉
🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
ORM
Caching in Prisma Client
Today’s release is a big one, as we introduce a new caching layer into Prisma ORM. But why the need for a caching layer?
In Prisma 7, the query compiler runs as a WebAssembly module directly on the JavaScript main thread. While this simplified the architecture by eliminating the separate engine process, it introduced a trade-off: every query now synchronously blocks the event loop during compilation.
For individual queries, compilation takes between 0.1ms and 1ms, which is barely noticeable in isolation. But under high concurrency this overhead adds up and creates event loop contention that affects overall application throughput.
For instance, say we have a query that is run over and over, but is a similar shape:
// These two queries have the same shape:
const alice = await prisma.user.findUnique({ where: { email: 'alice@prisma.io' } })
const bob = await prisma.user.findUnique({ where: { email: 'bob@prisma.io' } })
Prior to v7.4.0, this would be reevaluated ever time the query is run. Now, Prisma Client will extract the user-provided values and replaces them with typed placeholders, producing a normalized query shape:
prisma.user.findUnique({ where: { email: %1 } }) // cache key
↑
%1 = 'alice@prisma.io' (or 'bob@prisma.io')
This normalized shape is used as a cache key. On the first call, the query is compiled as usual and the resulting plan is stored in an LRU cache. On every subsequent call with the same query shape, regardless of the actual values, the cached plan is reused instantly without invoking the compiler.
We have more details on the impact of this change and some deep dives into Prisma architecture in an upcoming blog post!
Partial Indexes (Filtered Indexes) Support
We're excited to announce Partial Indexes support in Prisma! This powerful community-contributed feature allows you to create indexes that only include rows matching specific conditions, significantly reducing index size and improving query performance.
Partial indexes are available behind the partialIndexes preview feature for PostgreSQL, SQLite, SQL Server, and CockroachDB, with full migration and introspection support.
Basic usage
Enable the preview feature in your schema:
generator client {
provider = "prisma-client-js"
previewFeatures = ["partialIndexes"]
}
Raw SQL syntax
For maximum flexibility, use the raw() function with database-specific predicates:
model User {
id Int @id
email String
status String
@@unique([email], where: raw("status = 'active'"))
@@index([email], where: raw("deletedAt IS NULL"))
}
Type-safe object syntax
For better type safety, use the object literal syntax for simple conditions:
model Post {
id Int @id
title String
published Boolean
@@index([title], where: { published: true })
@@unique([title], where: { published: { not: false } })
}
Bug Fixes
Most of these fixes are community contributions - thank you to our amazing contributors!
- prisma/prisma-engines#5767: Fixed an issue with PostgreSQL migration scripts that prevented usage of
CREATE INDEX CONCURRENTLYin migrations - prisma/prisma-engines#5752: Fixed BigInt precision loss in JSON aggregation for MySQL and CockroachDB by casting BigInt values to text (from community member polaz)
- prisma/prisma-engines#5750: Fixed connection failures with non-ASCII database names by properly URL-decoding database names in connection strings
- #29155: Fixed silent transaction commit errors in PlanetScale adapter by ensuring COMMIT failures are properly propagated
- #29141: Resolved race condition errors (EREQINPROG) in SQL Server adapter by serializing commit/rollback operations using mutex synchronization
- #29158: Fixed MSSQL connection string parsing to properly handle curly brace escaping for passwords containing special characters
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
7.3.0
2 months ago
Today, we are excited to share the 7.3.0 stable release 🎉
🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
ORM
- #28976: Fast and Small Query Compilers
We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new
compilerBuildoption for the client generator block inschema.prismawith two options:fastandsmall. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, thefastmode is used, but this can be set by the user:
generator client {
provider = "prisma-client"
output = "../src/generated/prisma"
compilerBuild = "fast" // "fast" | "small"
}
We still have more in progress for performance, but this new compilerBuild option is our first step toward addressing your concerns!
-
#29005: Bypass the Query Compiler for Raw Queries Raw queries (
$executeRaw,$queryRaw) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead. -
#28965: Update MSSQL to v12.2.0 This community PR updates the
@prisma/adapter-mssqlto use MSSQL v12.2.0. Thanks Jay-Lokhande! -
#29001: Pin better-sqlite3 version to avoid SQLite bug An underlying bug in SQLite 3.51.0 has affected the
better-sqlite3adapter. We’ve bumped the version that powers@prisma/better-sqlite3and have pinned the version to prevent any unexpected issues. If you are using@prisma/better-sqlite3, please upgrade to v7.3.0. -
#29002: Revert
@mapenums to v6.19.0 behavior In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the@mapfunction. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion. -
prisma-engines#5745: Cast BigInt to text in JSON aggregation When using
relationJoinswith BigInt fields in Prisma 7, JavaScript'sJSON.parseloses precision for integers larger thanNumber.MAX_SAFE_INTEGER(2^53 - 1). This happens because PostgreSQL'sJSONB_BUILD_OBJECTreturns BigInt values as JSON numbers, which JavaScript cannot represent precisely.// Original BigInt ID: 312590077454712834 // After JSON.parse: 312590077454712830 (corrupted!)This PR cast BigInt columns to
::textinsideJSONB_BUILD_OBJECTcalls, similar to howMONEYis already cast to::numeric.-- Before JSONB_BUILD_OBJECT('id', "id") -- After JSONB_BUILD_OBJECT('id', "id"::text)
This ensures BigInt values are returned as JSON strings, preserving full precision when parsed in JavaScript.
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
6.19.2
2 months ago
Today, we are issuing a 6.19.2 patch release in the Prisma 6 release line. It fixes an issue with Prisma Accelerate support in some edge runtime configurations when the @prisma/client/edge entrypoint is not being used.
Changes:
- https://github.com/prisma/prisma/pull/28934
7.2.0
3 months ago
Today, we are excited to share the 7.2.0 stable release 🎉
🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Highlights
ORM
- #28830: feat: add
sqlcommenter-query-insightsplugin- Adds a new SQL commenter plugin to support query insights metadata.
- #28860: feat(migrate): add
-urlparam fordb pull,db push,migrate dev- Adds a
-urlflag to key migrate commands to make connection configuration more flexible.
- Adds a
- #28895: feat(config): allow undefined URLs in e.g.
prisma generate- Allows certain workflows (such as
prisma generate) to proceed even when URLs are undefined.
- Allows certain workflows (such as
- #28903: feat(cli): customize
prisma initbased on the JS runtime (Bun vs others)- Makes
prisma inittailor generated setup depending on whether the runtime is Bun or another JavaScript runtime.
- Makes
- #28846: fix(client-engine-runtime): make
DataMapperErroraUserFacingError- Ensures
DataMapperErroris surfaced as a user-facing error for clearer, more actionable error reporting.
- Ensures
- #28849: fix(adapter-{pg,neon,ppg}): handle 22P02 error in Postgres
- Improves Postgres adapter error handling for invalid-text-representation errors (
22P02).
- Improves Postgres adapter error handling for invalid-text-representation errors (
- #28913: fix: fix byte upserts by removing legacy byte array representation
- Fixes byte upsert behavior by removing a legacy byte-array representation path.
- #28535: fix(client,internals,migrate,generator-helper): handle multibyte UTF-8 characters split across chunk boundaries in byline
- Prevents issues when multibyte UTF-8 characters are split across chunk boundaries during line processing.
- #28911: fix(cli): make
prisma version --jsonemit JSON only to stdout- Ensures machine-readable JSON output is emitted cleanly to stdout without extra noise.
VS Code Extension
- #1950: fix: TML-1670 studio connections
- Resolves issues related to Studio connections, improving reliability for VS Code or language-server integrations.
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.
Enterprise support
Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.
With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.
6.19.1
3 months ago
Today, we are issuing a patch release for Prisma 6 that includes a fix for a diffing bug introduced in Prisma 6.13.1, which led to incorrectly reported empty diffs.
Changes
- https://github.com/prisma/prisma-engines/pull/5706