Prisma 5.9.0 — Release Notes & Engineering Impact

Today, we are excited to share the `5.9.0` stable release 🎉  🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check) about the release.** This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks: - Improve the performance of relation queries by introducing JOINs (see [last release](https://github.com/prisma/prisma/releases/tag/5.8.0)). - Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0)). ## Highlights ### Optimized result sets for more efficient queries We continue our efforts of the performance of Prisma Client queries. In [`5.1.0`](https://github.com/prisma/prisma/releases/tag/5.1.0), we introduced the `RETURNING` keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of `RETURNING` to SQLite and a broader range of queries for existing databases (e.g. `delete` on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs: - [feat(qe): avoid extra select on delete queries](https://github.com/prisma/prisma-engines/pull/4595) - [feat(qe): enable queries with returning for sqlite](https://github.com/prisma/prisma-engines/pull/46) ### SQL Server: Return proper error for unreachable database When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct `P1001` error instead of failing without an error. Learn more in this PR: [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://github.com/prisma/prisma/issues/11407). ## Fixes and improvements ### Prisma Client - [Skip unnecessary `select` queries on create/update/delete](https://github.com/prisma/prisma/issues/8069) - [.prisma/client: Name can't start with a dot](https://github.com/prisma/prisma/issues/17685) - [Nested json is transformed to string when used “$type” key in object](https://github.com/prisma/prisma/issues/21454) - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://github.com/prisma/prisma/issues/22610) ### Prisma Migrate - [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://github.com/prisma/prisma/issues/11407) - [Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14](https://github.com/prisma/prisma/issues/19775) - [`ERROR: column "..." being dropped, try again later` when applying migrations with CRDB 23.1](https://github.com/prisma/prisma/issues/20851) ### Language tools (e.g. VS Code) - [Extension wrongfully suggests Json as a valid type completion on Sqlite](https://github.com/prisma/language-tools/issues/1638) ## Company news ### Test edge functions support in Early Access Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using [Prisma Accelerate](https://www.prisma.io/data-platform/accelerate). However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0). ### We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. [Learn more in this technical deep dive](https://www.prisma.io/blog/accelerate-ipv6-first) into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate. ## Credits Huge thanks to @laplab, @Druue, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @almeidx, @victorgdb, @tinola, @sampolahtinen, @AikoRamalho, @petradonka for helping!