⬆️ Bump prisma from 2.30.3 to 3.4.0

[dependabot]

Bumps prisma from 2.30.3 to 3.4.0.

Release notes

Sourced from prisma's releases.

3.4.0

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

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

Major improvements & new features

Support for PostgreSQL 14

We are pleased to announce that Prisma version 3.4.0 provides support for PostgreSQL 14. For a full list of our supported databases and their versions, see our documentation.

MongoDB

Support for Order By Aggregate Group

In Prisma version 3.4.0, we add support on MongoDB databases for using the ORDER BY clause in an aggregate function. This was previously available for relational databases.

For example, if the data about your application's users includes their city of residence, you can determine which cities have the largest user groups. The following query sorts each city group by the number of users in that group, and returns the results in descending order (largest group first):

const groupBy = await prisma.user.groupBy({
  by: ['city'],
  _count: {
    city: true,
  },
  orderBy: {
    _count: {
      city: 'desc',
    },
  },
})

For more information refer to our documentation about ordering by groups.

Initial support for MongoDB in prisma db push

The prisma db push command is used to sync your Prisma schema and your database schema in development.

Because MongoDB has a unique approach to database schema management, this initial release only syncs @unique, @@unique and @@index annotations in your schema.

Let's look at a quick example using this Prisma schema:

datasource db {
  provider = "mongodb"
  url = env("DATABASE_URL")
}
generator js {
</tr></table>

... (truncated)

Commits

• a7c5041 chore(deps): update engines to 3.4.0-27.1c9fdaa9e2319b814822d6dbfd0a69e1fcc13...
• 1630040 chore(deps): update engines to 3.4.0-26.1898a7e5df867375e884c34f55e5cd49ede6a...
• ec06e8a chore(deps): update engines to 3.4.0-24.b0917542adedc6295266bb02ac95957d0cb68...
• 73023da chore(deps): update engines to 3.4.0-22.26fe5b2d39db3c0d3ae0df931cac134589e1c...
• e6c418c feat: Allow prisma db push on mongodb (#10041)
• 977968d chore(deps): update engines to 3.4.0-21.e62252643e73b975cc07ea75d85ffe7ef1c39...
• 29f8a94 chore(deps): update engines to 3.4.0-20.25ff8286101ce9d75ed64728222d5d9beba7d...
• 56c9102 chore(deps): update engines to 3.4.0-19.5e17612f2f7594488874074e686d1497bad1e...
• 95f1b57 feat(dbpull): --composite-type-depth for mongodb (#9998)
• 78c279d fix(client): benchmark (#9987)
• 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)