chore(deps): update prisma monorepo to v5.9.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	5.8.1 -> 5.9.0
@prisma/generator-helper (source)	5.8.1 -> 5.9.0
@prisma/internals (source)	5.8.1 -> 5.9.0
prisma (source)	5.8.1 -> 5.9.0

---

Release Notes

prisma/prisma (@​prisma/client)

v5.9.0

Compare Source

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 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).
• Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our survey).

Highlights

Optimized result sets for more efficient queries

We continue our efforts of the performance of Prisma Client queries. In 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
• feat(qe): enable queries with returning for sqlite

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.

Fixes and improvements

Prisma Client

• Skip unnecessary select queries on create/update/delete
• .prisma/client: Name can't start with a dot
• Nested json is transformed to string when used “$type” key in object
• Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit

Prisma Migrate

• SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url
• Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14
• ERROR: column "..." being dropped, try again later when applying migrations with CRDB 23.1

Language tools (e.g. VS Code)

• Extension wrongfully suggests Json as a valid type completion on Sqlite

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. 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.

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 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!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.