Prisma

Latest version: v0.15.0

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 44

5.4.2

Today, we are issuing the `5.4.2` patch release.

Fix in Prisma Client

- [5.4.0 subquery has too many columns](https://github.com/prisma/prisma/issues/21356)
- [One-to-Many relationship does not join on the specified field](https://github.com/prisma/prisma/issues/21366)

5.4.1

Today, we are issuing the `5.4.1` patch release.

Fix in Prisma Client

- [Invalid `….findMany()` invocation: The column `j1.id` does not exist in the current database.](https://github.com/prisma/prisma/issues/21352)

Fix in `prisma/adapter-planetscale`
- [Planetscale driver: unsupported column type NULL](https://github.com/prisma/prisma/issues/21369)

5.4.0

sql
SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?;
UPDATE `prisma`.`User` SET `firstName` = ? WHERE `prisma`.`User`.`id` IN (?) AND `prisma`.`User`.`email` = ?;
SELECT `User`.`id` FROM `User` WHERE `User`.`id` = ?;


Fixes and improvements

Prisma Client

- [Unnecessary `SELECT` may be generated by `upsert()`](https://github.com/prisma/prisma/issues/5686)
- [Inefficient deleteMany query generation](https://github.com/prisma/prisma/issues/7232)
- [Prisma can generate an overly complex and inefficient query in some cases](https://github.com/prisma/prisma/issues/7894)
- [`deleteMany` optimisation](https://github.com/prisma/prisma/issues/8239)
- [CockroachDB: Highly Variable Query Response Times](https://github.com/prisma/prisma/issues/11317)
- [Extremely poor relation where clause query](https://github.com/prisma/prisma/issues/14688)
- [Enums loaded as part of transaction after `UPDATE`, slowing down transaction.](https://github.com/prisma/prisma/issues/14955)
- [ MongoDB `deleteMany` seems to send 2 identical read queries first before triggering the actual delete](https://github.com/prisma/prisma/issues/15085)
- [Query validation messages reference color output even if colors are not enabled](https://github.com/prisma/prisma/issues/17706)
- [Prisma generates unnecessary subquery, which is inefficient](https://github.com/prisma/prisma/issues/17879)
- [Unnecessary INNER JOIN when doing nested queries](https://github.com/prisma/prisma/issues/18343)
- [Semver checks for yarn and typescript could potentially fail](https://github.com/prisma/prisma/issues/18751)
- [Prisma overrides type caching when in PGBouncer mode, causing 9,000 enum queries per second on a production system](https://github.com/prisma/prisma/issues/19325)
- [deleteMany generates double WHERE filter](https://github.com/prisma/prisma/issues/19950)
- [Prisma generate command crashes with `RustPanic: RuntimeError: panicked at 'internal error: entered unreachable code', query-engine/prisma-models/src/field/scalar.rs:93:50`](https://github.com/prisma/prisma/issues/20037)
- [Duplicated keys in `metrics` properties](https://github.com/prisma/prisma/issues/21069)
- [Prisma Client extension with method override and `jest-mock-extended` or `vitest-mock-extended` expects `never` input ](https://github.com/prisma/prisma/issues/21136)

Language tools (e.g. VS Code)

- [Auto-completion suggests attributes already present ](https://github.com/prisma/language-tools/issues/1326)
- [Quick Fix: when `schema` is defined in a block without the `schemas` attribute](https://github.com/prisma/language-tools/issues/1333)

Prisma Engines

- [CockroachDB: get_columns can hit inefficiency inside pg_class](https://github.com/prisma/prisma-engines/issues/4250)

Credits

Huge thanks to onichandame, fqazi, KhooHaoYit, alencardc, Oreilles, christianledgard, skyzh, alula, michaelpoellath, RobertCraigie, icanipa, jiashengguo, stephenwade, darthmaim, ludralph, Gerschtli, andyjy for helping!


💼 We're hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're currently hiring for the following roles:
- [Software Engineer](https://boards.greenhouse.io/prisma/jobs/6948042002)
- [Senior Software Engineer (Rust)](https://boards.greenhouse.io/prisma/jobs/6940273002)
- [Engineering Manager: Prisma Data Platform](https://boards.greenhouse.io/prisma/jobs/6927046002)

Feel free to read the job descriptions and apply using the links provided.

5.3.1

Today, we are issuing the `5.3.1` patch release.

Fix in Prisma Client

- [Duplicated keys in `metrics` properties](https://github.com/prisma/prisma/issues/21069)

5.3.0

🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20prisma%20release%20v5.3.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.3.0) about the release.** 🌟

Highlights

In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!

Improvements and bug fixes

We made the following changes:

Prisma Client improvements

- Validation for `undefined` values in arrays in `Json` fields
We added runtime validation for `undefined` values in arrays in `Json` fields. Prisma Client will now return an error when an array contains an `undefined` value. Therefore, we encourage you to add validation that either removes the value or transforms it to `null` if you stumble on the runtime validation:
ts
// Query
await prisma.user.findMany({
where: {
// JSON field
preferences: [undefined, '"theme": "dark"', null, ]
}
})

// Example error message on running the query
Can not use `undefined` value within array. Use `null` or filter out `undefined` values

- Performance improvements for models with many unique fields: This release improves Prisma Client’s memory consumption for models with many `unique` constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory.
- Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
- Metrics Preview feature improvements:
- We updated the counters and gauge properties
- We fixed the bug that caused the `prisma_pool_connections_open` metric to have a negative value in some cases.

Prisma Migrate improvements

- Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, `prisma db pull` would throw an error. We resolved this, and views are now ignored.
- Added the `PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK` environment variable that enables you to disable [advisory locking](https://www.prisma.io/docs/concepts/components/prisma-migrate/migrate-development-production#advisory-locking).

[VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) improvements

- Added support for rendering multi-line comments in tooltips when hovering on a block.
- Improved the auto-completion for composite types in other blocks.
- Added a Code Action that allows you to replace `SetDefault` with `NoAction` when using MySQL and the default/`foreignKeys` relation mode.

Fixes and improvements

Prisma Migrate

- [Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING](https://github.com/prisma/prisma/issues/16020)
- [MongoDB views should be ignored introspecting the database](https://github.com/prisma/prisma/issues/16179)
- [Error in Connector on MongoDB executing listIndex: "system.views"](https://github.com/prisma/prisma/issues/17006)
- [`prisma migrate deploy`: `MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'`](https://github.com/prisma/prisma/issues/19350)

Prisma Client

- [Remove all special cases for Data Proxy in our tests](https://github.com/prisma/prisma/issues/16101)
- [Segmentation fault on ARM64 Linux](https://github.com/prisma/prisma/issues/18510)
- [In the metrics feature a gauge & counter are swapped](https://github.com/prisma/prisma/issues/18760)
- [The prisma metrics `prisma_pool_connections_open` has a bug where it goes negative](https://github.com/prisma/prisma/issues/18761)
- [Prisma crashes with GraphQL queries of nested one-to-many relationship](https://github.com/prisma/prisma/issues/18787)
- [P1017 Server has closed the connection on linux_arm64](https://github.com/prisma/prisma/issues/19209)
- [`Error: socket hang up` on Linux/arm64](https://github.com/prisma/prisma/issues/19419)
- [Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)](https://github.com/prisma/prisma/issues/19743)
- [Prisma 5 drops `undefined` from Arrays when using Json fields with Postgres](https://github.com/prisma/prisma/issues/20325)
- [Suspected memory leak in Lambda function after upgrading from 4.10.1](https://github.com/prisma/prisma/issues/20799)
- [Error when generating - No unsupported field should reach that path](https://github.com/prisma/prisma/issues/20986)

Language tools (e.g. VS Code)

- [Models with multi line comments only show last line in tooltip](https://github.com/prisma/language-tools/issues/861)
- [Add VS Code quick fix / code action to replace `SetDefault` with `NoAction` when `provider = "mysql"` and `relationMode = "foreignKeys" | default`](https://github.com/prisma/language-tools/issues/1286)
- [Composite Types aren't offered as being auto-completable in other blocks](https://github.com/prisma/language-tools/issues/1495)

Credits

Huge thanks to alencardc, Oreilles, christianledgard, skyzh, alula, michaelpoellath, RobertCraigie, stephenwade for helping!

5.2.0

sql
SELECT "Post"."id", "Post"."title", "Post"."userId" FROM "Post" WHERE ("Post"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "User"."id" FROM "User" WHERE (1=1 AND "User"."id" IN ($1)) OFFSET $2
SELECT "User"."id", "User"."commentId" FROM "User" WHERE ("User"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
SELECT "Comment"."id" FROM "Comment" WHERE (1=1 AND "Comment"."id" IN ($1)) OFFSET $2
UPDATE "Comment" SET "body" = $1 WHERE ("Comment"."id" = $2 AND 1=1) RETURNING "Comment"."id"
SELECT "Post"."id", "Post"."title" FROM "Post" WHERE "Post"."id" = $1 LIMIT $2 OFFSET $3


Fixes and improvements

Prisma Client

- [CFW: Avoid including Query Engine when data proxy is enabled](https://github.com/prisma/prisma/issues/9597)
- [Local Prisma Studio does not work with Data Proxy](https://github.com/prisma/prisma/issues/12734)
- [Postinstall hook always generates non Data Proxy Prisma Client](https://github.com/prisma/prisma/issues/13608)
- [`limit` is gone when `findUnique` with include relation ](https://github.com/prisma/prisma/issues/14499)
- [`Cannot fetch data from service: include is not a function` Error while using Next.js with Data Proxy](https://github.com/prisma/prisma/issues/15395)
- [`take` key doesn't work correctly for nested query that returns one item with its nested children](https://github.com/prisma/prisma/issues/15623)
- [Prisma Client Edge: environment variables are not working with the "new" Module Worker syntax for Cloudflare Workers](https://github.com/prisma/prisma/issues/15958)
- [Add documentation to "PrismaClient is unable to be run in the browser"](https://github.com/prisma/prisma/issues/16153)
- [Change how Data Proxy Client deals with unsupported preview features](https://github.com/prisma/prisma/issues/17796)
- [Custom Prisma Client output location breaks Prisma Data Proxy in NextJS](https://github.com/prisma/prisma/issues/18227)
- [GetPayload type error since 4.16.1 "Two different types with this name exist, but they are unrelated."](https://github.com/prisma/prisma/issues/20422)
- [Browser bundle: Unhandled Runtime Error when upgrading to 5.1.0 from 5.0.0 ](https://github.com/prisma/prisma/issues/20480)
- [Prisma Client: `disconnect: true` does not appear to delete the foreign key in the returned data](https://github.com/prisma/prisma/issues/20491)
- [Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no `needs` and `count` method](https://github.com/prisma/prisma/issues/20499)
- [Upgrading from Prisma 5.0.0 -> 5.1.0 results in "TS2321: Excessive stack depth comparing types" error using `mockDeep<PrismaClient>()`](https://github.com/prisma/prisma/issues/20516)
- [Unnecessary reads for to-one nested updates](https://github.com/prisma/prisma/issues/20556)
- [Better error message if `prisma/client/edge` can not find environment variable](https://github.com/prisma/prisma/issues/20589)
- [5.1: Alias for old name for `<Model>CountOutputTypeDefaultArgs` does not exist](https://github.com/prisma/prisma/issues/20614)
- [Incorrect pagination for nested m2m chunked reads](https://github.com/prisma/prisma/issues/20624)


Prisma Migrate

- [RustPanic on `prisma generate` when Unsupported field defined in a Composite type](https://github.com/prisma/prisma/issues/19694)
- [Use PostgreSQL System Information Functions instead of manually joining fields](https://github.com/prisma/prisma/issues/19935)
- [Duplicate expression index comment whenever db pull is run](https://github.com/prisma/prisma/issues/20386)


Credits

Huge thanks to skyzh, alula, michaelpoellath, RobertCraigie, darthmaim, Gerschtli, andyjy, mejiaej, iurylippo, mrazauskas, coder246, RDIL for helping!

Page 6 of 44

Links

Releases

Has known vulnerabilities

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.