⬆️ Bump @prisma/client from 2.30.3 to 3.5.0

[dependabot]

Bumps @prisma/client from 2.30.3 to 3.5.0.

Release notes

Sourced from @​prisma/client's releases.

3.5.0

Today, we are excited to share the 3.5.0 stable release 🎉

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

Major improvements & new features

Order by relevance in full text search (PostgreSQL)

In 3.5.0, we've added support for ordering full text search results by relevance. Ordering by relevance gives you a way to order search results by the best match.

While this feature is useful standalone, it's most commonly used in combination with the full text search field in the where clause:

const query = "node.js developer"
const developers = await prisma.people.findMany({
  where: {
    bio: {
      // Only select people whose bio's contain "node.js developer"
      search: query,
    },
  },
  orderBy: {
    // Order that selection by query relevance.
    _relevance: {
      fields: ["bio"],
      search: query,
      sort: "desc",
    },
  },
})

Learn more in our documentation and if you run into any issues or have feedback for us, you can reach us in this issue.

More configuration options for indexes and constraints in the Prisma schema (Preview)

We are extending the syntax in the Prisma schema to add support for configuration of length and sort order. This applies to:

• indexes
• unique constraints
• primary key constraints

These new configuration options come with full support for the prisma db pull, prisma db push and prisma migrate dev commands, so index configuration can now be managed, evolved and deployed using Prisma's schema management tooling.

Two new arguments can now be specified per field:

• length (the maximum length of items in the index)
• sort (how an index is sorted)

... (truncated)

Commits

• bd925f0 chore(deps): update engines to 3.5.0-38.78a5df6def6943431f4c022e1428dbc3e833c...
• 5ae44b6 chore(deps): update engines to 3.5.0-37.471f775de5e67ec17de893781ae51484bbcbe...
• dba7c6f chore(deps): update engines to 3.5.0-36.ff8a96ee75472d6767c062b058972d1ceade1...
• 895780e fix(build): broken require for bundlers (#10222)
• ecebdad chore(deps): update engines to 3.5.0-35.46b1591db31dd417051309a9b64c74ed87406...
• fc87f3e chore: add docker-compose file for ARM64 machines (#10235)
• 6bc29e3 fix(cli,client): remove DEBUG binding to dotenv enableDebug (#10262)
• b03f1db fix(client): remove console.log (#10263)
• 2c01e6a chore(deps): update engines to 3.5.0-34.d2ab7a957cf9549aa842f3179c0527632d160...
• fcaf312 chore(client): data proxy improvements (#9893)
• 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 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 #7.