chore(deps): bump prisma from 4.15.0 to 5.10.2

[dependabot]

Bumps prisma from 4.15.0 to 5.10.2.

Release notes

Sourced from prisma's releases.

5.10.2

Today, we are issuing the 5.10.2 patch release.

Fix in Prisma CLI

• Invalid character error persists on 5.10.1 in Prisma Studio

5.10.1

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

5.10.0

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

// 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:

await prisma.user.findMany({
</tr></table> 

... (truncated)

Commits

• af6c2de fix(cli): studio when used with non-ascii chars
• 78c4be6 feat(cli): delete management token on logout (#23191)
• 11c76b8 feat(init): mention Accelerate in the Prisma schema (#23086)
• 0e92f9d feat(cli): next version (#23090)
• 19511a5 chore(deps): update definitelytyped (#23155)
• 4c57f19 chore(deps): update devdependencies patch (non-major) (#23157)
• 28d35ba chore(deps): update devdependencies patch (non-major) (#23117)
• 132fe17 refactor(cli/platform): optimize structure for CI runs (#23056)
• 99e91c6 fix(generator): use kill('SIGKILL') if SIGTERM was not enough (#23046)
• 3b202d3 chore(deps): update definitelytyped (#23037)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: dependencies.

[dependabot]

Superseded by #528.