[Snyk] Upgrade @prisma/client from 5.13.0 to 5.14.0

[DHurtado714-itesm]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @prisma/client from 5.13.0 to 5.14.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 92 versions ahead of your current version.

• The recommended version was released on 21 days ago.

Release notes

Package name: @prisma/client

• 5.14.0 - 2024-05-14
  

  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.

  With 5.14.0, Prisma ORM now rewrites queries to use a combination of $or and $eq operators, leading to dramatic performance increases for queries that include in operators or relation loading.

  Fixes and improvements

  Prisma Client

  • createMany() should return the created records
  • Generating Prisma client without any model in its schema
  • MongoDB: Performance issue with nested take on many-to-one relationship
  • Slow queries on MongoDB using include for relations
  • [MongoDB] Performance issue in findMany() query execution with in
  • MongoDB nested/include query slow
  • MongoDB Connector generates queries which do not take advantage of indices.
  • Mongodb Nested Queries Not Using Indexes
  • MongoDB slow delete with onDelete: SetNull
  • Slow query with many-to-one relationship on MongoDB
  • prisma init --with-model
  • Fixed version of @ opentelemetry/* dependencies
  • Usage of deprecated punycode module
  • Bug: D1 One-to-Many Relation INSERTs fail with The required connected records were not found. when using indices

  Prisma Migrate

  • Empty dbgenerated() still breaking for Unsupported() types
  • Validation error when shadowDatabaseUrl is identical to url (or directUrl)
  • MongoDB Query with 'in' condition will cause COLLSCAN, without leveraging indexes
  • "Not Authorised" when directly applying Prisma generated migrations to Cloudflare D1 with PRAGMA foreign_key_check;

  Language tools (e.g. VS Code)

  • make superior: model generate
  • Missing code autocomplete for referential actions with mongodb

  Company news

  Prisma Changelog

  Curious about all things Prisma? Be sure to check out the Prisma Changelog for updates across Prisma's products, including ORM, Accelerate, and Pulse!

  New product announcement: Prisma Optimize

  With this release, we are excited to introduce a new Prisma product. We’re calling it “Optimize” because that’s what it does! Let your favorite ORM also help you debug the performance of your application.

  Check out our announcement blog post for more details, including a demo video.

  Credits

  Huge thanks to @ pranayat, @ yubrot, @ skyzh, @ anuraaga, @ gutyerrez, @ avallete, @ ceddy4395, @ Kayoshi-dev for helping!

• 5.14.0-integration-static-wasm-worker-loader.5 - 2024-05-13
• 5.14.0-integration-static-wasm-worker-loader.4 - 2024-05-08
• 5.14.0-integration-static-wasm-worker-loader.3 - 2024-04-30
• 5.14.0-integration-static-wasm-worker-loader.2 - 2024-04-30
• 5.14.0-integration-static-wasm-worker-loader.1 - 2024-04-30
• 5.14.0-integration-schema-files-resolver.10 - 2024-05-14
• 5.14.0-integration-schema-files-resolver.9 - 2024-05-14
• 5.14.0-integration-schema-files-resolver.8 - 2024-05-10
• 5.14.0-integration-schema-files-resolver.7 - 2024-05-10
• 5.14.0-integration-schema-files-resolver.6 - 2024-05-08
• 5.14.0-integration-schema-files-resolver.5 - 2024-05-08
• 5.14.0-integration-schema-files-resolver.4 - 2024-05-08
• 5.14.0-integration-schema-files-resolver.3 - 2024-05-07
• 5.14.0-integration-schema-files-resolver.2 - 2024-05-07
• 5.14.0-integration-schema-files-resolver.1 - 2024-05-06
• 5.14.0-integration-engines-5-14-0-26-text-comp-multi-20f7cb6cf71d1ee66be7363748ca983d326e9db1.1 - 2024-05-14
• 5.14.0-integration-engines-5-14-0-22-integration-rust-1-78-wasm-fc926224322c04c61c76032c9985a1d4fdfee13f.2 - 2024-05-10
• 5.14.0-integration-engines-5-14-0-22-integration-rust-1-78-wasm-fc926224322c04c61c76032c9985a1d4fdfee13f.1 - 2024-05-10
• 5.14.0-integration-engines-5-14-0-19-fix-ds-url-rn-03c57ba9ba8eea9dfcf11c5382fdb6822d5aa3d2.1 - 2024-05-10
• 5.14.0-integration-engines-5-14-0-10-feat-create-many-and-return-31c187d29db487fb54d6bb593a851d2f9e5687a6.2 - 2024-05-02
• 5.14.0-integration-engines-5-14-0-10-feat-create-many-and-return-31c187d29db487fb54d6bb593a851d2f9e5687a6.1 - 2024-05-02
• 5.14.0-integration-engines-5-14-0-1-integration-vitess-constraint-fix-ca251465b6b966a5b9f61c3a8077ef99275ca330.2 - 2024-04-23
• 5.14.0-integration-engines-5-14-0-1-integration-vitess-constraint-fix-ca251465b6b966a5b9f61c3a8077ef99275ca330.1 - 2024-04-23
• 5.14.0-dev.77 - 2024-05-14
• 5.14.0-dev.76 - 2024-05-13
• 5.14.0-dev.75 - 2024-05-13
• 5.14.0-dev.74 - 2024-05-13
• 5.14.0-dev.72 - 2024-05-13
• 5.14.0-dev.71 - 2024-05-13
• 5.14.0-dev.70 - 2024-05-13
• 5.14.0-dev.69 - 2024-05-13
• 5.14.0-dev.68 - 2024-05-13
• 5.14.0-dev.67 - 2024-05-10
• 5.14.0-dev.66 - 2024-05-10
• 5.14.0-dev.65 - 2024-05-08
• 5.14.0-dev.64 - 2024-05-08
• 5.14.0-dev.63 - 2024-05-08
• 5.14.0-dev.62 - 2024-05-08
• 5.14.0-dev.61 - 2024-05-08
• 5.14.0-dev.60 - 2024-05-08
• 5.14.0-dev.59 - 2024-05-08
• 5.14.0-dev.58 - 2024-05-08
• 5.14.0-dev.57 - 2024-05-08
• 5.14.0-dev.56 - 2024-05-08
• 5.14.0-dev.55 - 2024-05-08
• 5.14.0-dev.54 - 2024-05-07
• 5.14.0-dev.53 - 2024-05-07
• 5.14.0-dev.52 - 2024-05-07
• 5.14.0-dev.51 - 2024-05-06
• 5.14.0-dev.50 - 2024-05-06
• 5.14.0-dev.49 - 2024-05-06
• 5.14.0-dev.48 - 2024-05-03
• 5.14.0-dev.47 - 2024-05-03
• 5.14.0-dev.46 - 2024-05-02
• 5.14.0-dev.44 - 2024-05-02
• 5.14.0-dev.43 - 2024-05-02
• 5.14.0-dev.42 - 2024-05-02
• 5.14.0-dev.41 - 2024-05-02
• 5.14.0-dev.40 - 2024-05-02
• 5.14.0-dev.39 - 2024-05-02
• 5.14.0-dev.38 - 2024-05-02
• 5.14.0-dev.36 - 2024-05-02
• 5.14.0-dev.35 - 2024-05-01
• 5.14.0-dev.34 - 2024-04-30
• 5.14.0-dev.33 - 2024-04-30
• 5.14.0-dev.32 - 2024-04-30
• 5.14.0-dev.31 - 2024-04-30
• 5.14.0-dev.30 - 2024-04-30
• 5.14.0-dev.28 - 2024-04-30
• 5.14.0-dev.27 - 2024-04-30
• 5.14.0-dev.26 - 2024-04-30
• 5.14.0-dev.25 - 2024-04-30
• 5.14.0-dev.24 - 2024-04-30
• 5.14.0-dev.23 - 2024-04-29
• 5.14.0-dev.22 - 2024-04-26
• 5.14.0-dev.21 - 2024-04-26
• 5.14.0-dev.20 - 2024-04-26
• 5.14.0-dev.19 - 2024-04-26
• 5.14.0-dev.18 - 2024-04-26
• 5.14.0-dev.16 - 2024-04-25
• 5.14.0-dev.14 - 2024-04-25
• 5.14.0-dev.13 - 2024-04-25
• 5.14.0-dev.12 - 2024-04-24
• 5.14.0-dev.11 - 2024-04-24
• 5.14.0-dev.9 - 2024-04-24
• 5.14.0-dev.6 - 2024-04-24
• 5.14.0-dev.5 - 2024-04-24
• 5.14.0-dev.4 - 2024-04-24
• 5.14.0-dev.3 - 2024-04-24
• 5.14.0-dev.2 - 2024-04-24
• 5.14.0-dev.1 - 2024-04-24
• 5.13.0 - 2024-04-23
  

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

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

  Highlights

  omit fields from Prisma Client queries (Preview)

  We’re excited to announce Preview support for the omit option within the Prisma Client query options. The highly-requested omit feature now allows you to exclude fields that you don’t want to retrieve from the database on a per-query basis.

  By default, when a query returns records, the result includes all scalar fields of the models defined in the Prisma schema. select can be used to return specific fields, while omit can now be used to exclude specific fields. omit lives at the same API level and works on all of the same Prisma Client model queries as select. Note, however, that omit and select are mutually exclusive. In other words, you can’t use both in the same query.

  To get started using omit, enable the omitApi Preview feature in your Prisma schema:

  // schema.prisma
  generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["omitApi"]
  }

  Be sure to re-generate Prisma Client afterwards:

  npx prisma generate

  Here is an example of using omit:

  // Includes all fields except password
  await prisma.user.findMany({
    omit: {
     password: true
    },
  })

  Here is an example of using omit with include:

  // Includes all user fields except user's password and title of user's posts
  await prisma.user.findMany({
    omit: {
     password: true
    },
    include: {
      posts: {
        omit: {
          title: true
        },
      },
    },
  })

  Expand to view the example Prisma schema

  model User {
  id Int @ id @ default(autoincrement())
  email String @ unique
  name String?
  password String
  posts Post[]
  }

  model Post {
  id Int @ id @ default(autoincrement())
  title String
  author User @ relation(fields: [authorId], references: [id])
  authorId Int
  }

  Many users have requested a global implementation of omit. This request will be accommodated in the future. In the meantime, you can follow the issue here.

  📣 Share your feedback: omitApi Preview feature

  📚 Documentation: omit - Prisma Client API Reference

  Fixes and improvements

  Prisma Migrate

  • Nicer Datamodel Type validation

  Prisma Client

  • MySQL upsert(): Internal error: Attempted to serialize empty result.
  • Mysql upsert() fails with "Attempted to serialize empty result."
  • Interactive Transaction API timing out after upgrading from 4.7.0 and above
  • MySQL and SQLite upsert(): Internal error: Attempted to serialize empty result.
  • MySQL upsert(): Internal error: Attempted to serialize empty result.
  • MongoDB upsert(): Internal error: Attempted to serialize empty result.
  • MongoDB upsert(): Internal error: Attempted to serialize empty result
  • Relation mode + upsert(): Internal error: Attempted to serialize empty result.
  • Internal error: Attempted to serialize empty result. on upsert() for update case in different databases (when using relationMode=prisma explicitly or implicitly [MongoDB])
  • Postgres upsert(): Internal error: Attempted to serialize empty result when relationMode = "prisma" is used
  • ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using Powershell)

  Credits

  Huge thanks to @ ospfranco, @ pranayat, @ yubrot, @ skyzh, @ anuraaga, @ yehonatanz, @ arthurfiorette, @ elithrar, @ tockn, @ Kuhave, @ obiwac for helping!

from @prisma/client GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs