search

libscie / ResearchEquals.com

Research module server
https://researchequals.com
MIT License
86 stars 10 forks source link

build(deps): bump @prisma/client from 5.9.1 to 5.14.0 #2084

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 1 month ago

Bumps @prisma/client from 5.9.1 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 compatibility score

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)
dependabot[bot] commented 2 weeks ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.