chore(deps): bump @prisma/internals from 4.10.1 to 5.2.0 in /packages/generator

[dependabot]

Bumps @prisma/internals from 4.10.1 to 5.2.0.

Release notes

Sourced from @​prisma/internals's releases.

5.2.0

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Improved Prisma Client experience for Prisma Accelerate and Data Proxy

In this release, we’ve made the following improvements to Prisma Client when using Prisma Accelerate or Prisma Data Proxy:

• Prisma Client will now automatically determine how it should connect to the database depending on the protocol in the connection string. If the connection string starts with prisma://, Prisma Client will try to connect to your database using Prisma Accelerate or Prisma Data Proxy.

• Prisma Studio now works with Prisma Data Proxy and Prisma Accelerate.

• We’ve introduced a new --no-engine flag which will prevent a Query Engine file from being included in the generated Prisma Client. This flag will also help ensure the bundle size of your application remains small by excluding the Query Engine files from the generated Prisma Client.

  prisma generate --no-engine

  The --data-proxy and --accelerate flags have not been removed but are now aliases for the new --no-engine flag.

  We recommend using the --no-engine flag when generating Prisma Client that uses either Accelerate or Data Proxy.

Simplified connection string override in Prisma Client

This release simplifies the API used when programmatically overriding the connection string by introducing the datasourceUrl property in Prisma Client’s constructor. This means you do not have to use the datasource name defined in your Prisma schema.

const prisma = new PrismaClient({
  datasourceUrl: "postgresql://johndoe:randompassword@localhost:5432/mydb",
})

Query performance improvements

Continuing our work from 5.1.0 we made further performance improvements around the queries Prisma executes, targeting one-to-many relation fields and nested updates.

Use LIMIT in one-to-many relations on a single parent

In cases where there is a single parent with a one-to-many relation included (findFirst, findUnique, findMany({ take: 1 })), we now utilize LIMIT at the database level to restrict the number of related items returned instead of retrieving all related items into memory and performing a take in memory.

For situations where you have many related objects but only need a few, you should see a dramatic improvement in speed and memory usage.

Note: we are still working on bringing this improvement to other parts of Prisma Client in upcoming releases. If multiple parent records are returned, the previous behavior is used.

Further improvements for nested writes

Thanks to our introduction of using RETURNING in some cases in 5.1.0, we could now improve performance in nested writes by removing reload nodes. This will now result in one less query per relation traversed in a nested write. For more info, check out the pull request.

Prisma Client query

... (truncated)

Commits

• 25258e0 chore(deps): update engines to 5.3.0-1.98bd6d18365f86d632686c26d1b26d8e054c67...
• 02164a6 chore(deps): update engines to 5.2.0-25.2804dc98259d2ea960602aca6b8e7fdc03c17...
• b3a29b8 refactor(cli): improve generation hints (#20731)
• 9ff064e chore(deps): update engines to 5.2.0-24.0bc8ee687eb17771fa7ca5167bcad38f8f2d0...
• 21a7d9b fix(client): remove data proxy links and mentions (#20716)
• 6730894 feat(client, cli): --no-engine (#20692)
• fb19dcd chore(deps): update engines to 5.2.0-22.1071f46b469e8756c48d0a5f9f6502c881d7c...
• c4d0c6f chore(deps): update engines to 5.2.0-21.0d2ee4d3fe757d532d33fc6f961d61b74f110...
• 83af57e chore(deps): update engines to 5.2.0-20.be8d0a6d55ca9598bb45d76c8f9490c144eb9...
• fdaa984 feat(client, cli): dynamic prisma:// urls engine loading (#20594)
• 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]

Superseded by #29.