⬆️ Bump @prisma/client from 5.10.2 to 5.14.0

[dependabot[bot]]

Bumps @prisma/client from 5.10.2 to 5.14.0.

Release notes

Sourced from @​prisma/client's releases.

5.14.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release. 🌟

Highlights

Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

createManyAndReturn()

We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.

Here’s an example of creating multiple posts and then immediately returning those posts.

const postBodies = req.json()['posts']
const posts = prisma.post.createManyAndReturn({
data: postBodies
});
return posts

Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.

const postBodies = req.json()['posts']
const postTitles = prisma.post.createManyAndReturn({
data: postBodies,
select: {
title: true,
},
});
return postTitles

Full documentation for this feature can be found in the Prisma Client API Reference.

Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.

MongoDB performance improvements

Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.

... (truncated)

Commits

• e0006b1 chore(deps): update engines to 5.14.0-25.e9771e62de70f79a5e1c604a2d7c8e2a0a87...
• 271d834 chore(deps): update engines to 5.14.0-24.879beb2a005f47f60608de797a554c8a500e...
• d2701d4 feat: create no models flag for generate command (#24160)
• 51ff5e4 chore(deps): update engines to 5.14.0-23.079da82321947525558fa7146f7737149538...
• ea28e76 chore(deps): update dependency wrangler to v3.55.0 (#24147)
• 7e66bc6 chore(deps): update engines to 5.14.0-21.6eec1600785bbff7acedfa57bc6826cdac2e...
• 6fcc818 feat(cli): add prismaSchemaFolder support to prisma generate via `mergeSc...
• 23aba0b docs: remove references to Prisma Slack (#24128)
• 52589ae chore: Remove issue link from "Client did not initialize yet" (#24117)
• c22724e feat(cli): ground work for prismaSchemaFolder, implementing validate, `form...
• 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 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)

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: ed2c627286a9a8dc0d5212ac35f9fc1e9c820d98

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
quri-hub	✅ Ready (Inspect)	Visit Preview	Jun 6, 2024 6:05pm
quri-ui	✅ Ready (Inspect)	Visit Preview	Jun 6, 2024 6:05pm
squiggle-components	✅ Ready (Inspect)	Visit Preview	Jun 6, 2024 6:05pm
squiggle-website	✅ Ready (Inspect)	Visit Preview	Jun 6, 2024 6:05pm

[vercel[bot]]

Deployment failed with the following error:

Too many requests - try again in 1 minute (more than 60, code: "api-deployments-flood").

[berekuk]

@dependabot rebase

[dependabot[bot]]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.