Prisma

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

Fix in Prisma Client / Prisma CLI

- [Error: Invalid character when schema.prisma includes Chinese/Non-ASCII characters in a comment](https://github.com/prisma/prisma/issues/23201)

Today, we are excited to share the `5.10.0` stable release 🎉

🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/post?text=Check%20out%20the%20latest%20%40prisma%20release%20v5.10.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps%3A%2F%2Fgithub.com%2Fprisma%2Fprisma%2Freleases%2Ftag%2F5.10.0) about the release.**

Highlights

Optimized relation queries in MySQL (Preview)

This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the `relationJoins` Preview feature with the `mysql` database provider, you now also get access to the `relationLoadStrategy` option in relation queries that let you choose whether you want to merged relations on the application- or database-level.

If you enable the `relationJoins` Preview feature, you can choose between the `join` and `query` options:

- `join` (default): Sends a single query to the database and joins the data on the database-level.
- `query`: Sends multiple queries to the database and joins the data on the application-level.

To get started, enable the Preview feature in your Prisma schema:

prisma
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["relationJoins"]
}


Be sure to re-generate Prisma Client afterwards:


npx prisma generate


And finally, specify the relation loading strategy for your relation query via the `relationLoadStrategy` option as follows:

ts
await prisma.user.findMany({
relationLoadStrategy: 'join', // or 'query'
include: {
posts: true,
},
})


Note that in the example above, the `relationLoadStrategy` could be omitted altogether because `join` is used as the default value.

A few notes about `relationLoadStrategy` support on MySQL:

- `relationLoadStrategy` is supported for MySQL v8.0.14 and higher. MariaDB is not supported.
- Prisma ORM uses correlated sub-queries for MySQL (as opposed to `LATERAL` JOINs which are used on PostgreSQL).


Configure transaction options in the `PrismaClient` constructor

This feature enables you to configure the following transaction options on a global level via the `PrismaClient` constructor:

- `isolationLevel`: Sets the [transaction isolation level](https://www.prisma.io/docs/orm/prisma-client/queries/transactions#transaction-isolation-level). By default, this is set to the value currently configured in your database.
- `timeout`: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.
- `maxWait`: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.

Here is an example of how you can set this value globally for all transactions:

ts
const prisma = new PrismaClient({
transactionOptions: {
isolationLevel: 'ReadCommitted',
timeout: 1_000, // 1 sec
maxWait: 2_000 // 2 sec
}
})


Thanks a lot to our fantastic community member [`tockn`](https://github.com/tockn), who took the initiative to implement this feature in Prisma ORM 🎉

Note that you can still override the global values by [setting them on a particular transaction](https://www.prisma.io/docs/orm/prisma-client/queries/transactions#transactions-options).

New `P2037` code for “Too many database connections opened” errors

We introduced a new error code for “Too many database connections opened” errors: `P2037`. You can find all error codes in our [documentation](https://www.prisma.io/docs/orm/reference/error-reference#prisma-client-query-engine).

Access the Prisma Data Platform via Prisma CLI

Now available in Early Access, you can manage your workspace and configure [Prisma Accelerate](https://www.prisma.io/docs/accelerate) and [Prisma Pulse](https://www.prisma.io/docs/pulse) directly from the terminal.

Visit our [docs](https://www.prisma.io/docs/platform/platform-cli/commands) to learn more about the integration and try it out for yourself!

Fixes and improvements

Prisma Client

- [called `Option::unwrap()` on a `None` value when using the relationJoins preview feature with driver adapters](https://github.com/prisma/prisma/issues/22294)
- [[5.9.0 Bug] `Prisma.TransactionClient` appears to be missing types](https://github.com/prisma/prisma/issues/22870)
- [Error after Upgrading from 5.8.1 to 5.9.0](https://github.com/prisma/prisma/issues/22875)
- [[5.9.0] `prisma/client` in Next.js middleware](https://github.com/prisma/prisma/issues/22877)
- [[v5.9.0] `$extends` always return `any`](https://github.com/prisma/prisma/issues/22884)
- [Prisma edge runtime error](https://github.com/prisma/prisma/issues/22886)
- [[5.9.0] All queries result in any type](https://github.com/prisma/prisma/issues/22888)
- [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.`](https://github.com/prisma/prisma/issues/22889)
- [[5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.](https://github.com/prisma/prisma/issues/22893)
- [v5.9.0 / Don't generate type. And the error from the previous version is still there](https://github.com/prisma/prisma/issues/22896)
- [[5.9.0] Getting strange types after generating](https://github.com/prisma/prisma/issues/22903)
- [relationJoins: "The column `t3.bookGenreTitle` does not exist in the current database"](https://github.com/prisma/prisma/issues/22926)
- [Missing export prisma/client/generator-build](https://github.com/prisma/prisma/issues/22927)
- [`relationJoins` preview feature: called `Option::unwrap()` on a `None` value](https://github.com/prisma/prisma/issues/22971)

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

Fixes in Prisma Client

In `5.9.0` we have changed our conditional exports in `prisma/client`. This resulted in broken types for TypesScript users using certain combinations of `module`/`moduleResolution` settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.

You can now try out `5.9.1` and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report

- [[5.9.0] Getting strange types after generating 22903](https://github.com/prisma/prisma/issues/22903)
- [v5.9.0 / Don't generate type. And the error from the previous version is still there 22896](https://github.com/prisma/prisma/issues/22896)
- [[5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22893](https://github.com/prisma/prisma/issues/22893)
- [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #22889](https://github.com/prisma/prisma/issues/22889)
- [[5.9.0] All queries result in any type 22888](https://github.com/prisma/prisma/issues/22888)
- [Prisma edge runtime error 22886](https://github.com/prisma/prisma/issues/22886)
- [please how i cant fix this message issues 22885](https://github.com/prisma/prisma/issues/22885)
- [[v5.9.0] $extends always return any 22884](https://github.com/prisma/prisma/issues/22884)
- [[5.9.0] prisma/client in Next.js middleware 22877](https://github.com/prisma/prisma/issues/22877)
- [Error after Upgrading from 5.8.1 to 5.9.0 22875](https://github.com/prisma/prisma/issues/22875)
- [[5.9.0 Bug] Prisma.TransactionClient appears to be missing types 22870](https://github.com/prisma/prisma/issues/22870)

Note: many issues are duplicates.

Major changes

* chore(prisma): upgrade prisma to v5.9.0 (1167) steebchen

Contributors

steebchen

----

**Full Changelog**: https://github.com/steebchen/prisma-client-go/compare/v0.32.1...v0.33.0

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

Fix in Prisma Client

- [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://github.com/prisma/prisma/issues/22610).

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

Highlights

Happy New Year from your friends at Prisma! 🎊

In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉

`relationJoins` improvements: Relation loading strategy per query (Preview)

In version [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0), we released `relationJoins` into Preview. The `relationJoins` feature enables support for `JOIN`s for relation queries.

This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.

You can now load relation data using either of the following strategies:

- `join` — uses `JOIN`s to fetch relation data
- `query` — uses separate queries to fetch relation data

When the `relationJoins` Preview feature is enabled, by default, the relation fetching strategy used is `join`. You can override the default behavior by using the `relationLoadStrategy` query option.

To get started, enable the Preview feature:

tsx
// schema.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["relationJoins"]
}


… and specify the relation loading strategy for your query as follows:

tsx
await prisma.user.findMany({
relationLoadStrategy: 'query',
include: {
posts: true,
},
})


Try it out and [share your feedback](https://github.com/prisma/prisma/discussions/22288) and create a [bug report](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&projects=&template=bug_report.yml) if you encounter any issues.

Survey: Edge functions support

We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by [submitting a response to our survey](https://pris.ly/survey/edge-functions-release-notes). By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.

Fixes and improvements

Prisma Client

- [Log output of Node-API library engine is different](https://github.com/prisma/prisma/issues/9039)
- [`target` and `timestamp` are undefined in `info` events in Data Proxy client](https://github.com/prisma/prisma/issues/18479)
- [Wrong types of `timestamp` and `duration` in query events with Data Proxy](https://github.com/prisma/prisma/issues/18482)
- [Using `citext` fields with neon database driver causes conversion error](https://github.com/prisma/prisma/issues/21807)
- [Add FreeBSD 14 as a new platform](https://github.com/prisma/prisma/issues/22228)
- [PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }](https://github.com/prisma/prisma/issues/22298)
- [Int[] return as null](https://github.com/prisma/prisma/issues/22303)

Prisma Migrate

- [Prisma Migrate errors with `Environment is non-interactive` when `VERCEL` env var is defined](https://github.com/prisma/prisma/issues/22380)

Language tools (e.g. VS Code)

- [Add quickfix for `Error validating field 'id' in model 'Post': MongoDB 'default(auto())' fields must have 'ObjectId' native type.`](https://github.com/prisma/language-tools/issues/1548)
- [Append mention of update to "preview feature not known" error message](https://github.com/prisma/language-tools/issues/1612)

Credits

Huge thanks to anuraaga, onichandame, LucianBuzzo, RobertCraigie, fqazi, KhooHaoYit, alencardc, Oreilles, tinola, AikoRamalho, luxaritas for helping!

Company news

🎉 A billion queries and counting: Prisma Accelerate

[Prisma Accelerate](https://pris.ly/accelerate-home-orm-release-1), our global database cache has served over 1 billion queries since its General Availability launch.

We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!

🔮 Prisma ORM Ecosystem

Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? [Let us know](https://prisma-data.typeform.com/to/DYEjFIVx).

We would like to learn about it and feature it on our [Ecosystem page](https://www.prisma.io/ecosystem).

💼 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. Check out our [Careers page](https://prisma.io/careers) for open positions.