Prisma 5.3.0 — Release Notes & Engineering Impact

🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%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!