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

[David-Besse]

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.14.0 to 5.15.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 95 versions ahead of your current version.

• The recommended version was released on 23 days ago.

Release notes

Package name: @prisma/client

• 5.15.0 - 2024-06-04
  

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

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

  Highlights

  Multi-File Prisma Schema support

  Prisma ORM 5.15.0 features support for multi-file Prisma Schema in Preview.

  This closes a long standing issue and does so in a clean and easy to migrate way.

  To get started:

  1. Enable the prismaSchemaFolder Preview feature by including it in the previewFeatures field of your generator.
     datasource db {
     provider = "postgresql"
     url = env("DATABASE_URL")
     }

     generator client {
     provider = "prisma-client-js"
     previewFeatures = ["prismaSchemaFolder"]
     }
     

  2. Create a schema subdirectory under your prisma directory.
  3. Move your schema.prisma into this directory.

  You are now set up with a multi-file Prisma Schema! Add as many or as few .prisma files to the new prisma/schema directory.

  When running commands where a Prisma Schema file is expected to be provided, you can now define a Prisma Schema directory. This includes Prisma CLI commands that use the --schema option as well as defining schema via package.json

  Our tooling has also been updated to handle multiple Prisma Schema files. This includes our Visual Studio Code extension and tools like database introspection, which will deposit new models in a introspected.prisma file. Existing models will be updated in the file they are found.

  To learn more, please refer to our official documentation and announcement blog post. If you try out prismaSchemaFolder, please let us know!

  Interesting Bug Fixes

  Fix for PostgreSQL prepared statement caching for raw queries

  This release fixes a nasty bug with the caching of prepared statements in raw Prisma Client queries that affected PostgreSQL when you ran the same SQL statement with differently typed paramters. This should not fail any more.

  Fix for SQL Server introspection of (deprecated) CREATE DEFAULT

  Our Introspection logic crashed on encountering certain multi-line CREATE DEFAULT, a deprecated way to define defaults in SQL Server. As many SQL Server users are working with established databases, this happened frequently enough that we now explicitly ignore these defaults instead of crashing.

  Fix for Cloudflare D1’s lower parameter limit

  Cloudflare’s D1 has a lower parameter limit than local SQLite, which caused bigger queries to fail. We adapted that limit to the D1 default for @ prisma/adapter-d1, which will avoid such failures.

  Fix for Cloudflare D1’s different PRAGMA support

  Our generated migration SQL for SQLite did not always work for Cloudflare D1, because of differences in the supported pragmas. We adapted the SQL to work in both local SQLite and Cloudflare D1.

  Fixes and improvements

  Prisma Migrate

  • Crash on multiline defaults introspection on MSSQL
  • Error: [libs\sql-schema-describer\src\mssql.rs:315:30] called Result::unwrap() on an Err value: "Couldn't parse default value: create default [dbo].[member_notification_cancel_flags] as 0\r\n"
  • Error: [libs\sql-schema-describer\src\mssql.rs:315:30] called Result::unwrap() on an Err value: "Couldn't parse default value: create default d_password as 'D,73' "
  • Crash introspecting MSSQL database with DEFAULTs
  • doing introspection on a SQL Server 2018 DB - for Dynamic GP get the following error.
  • Error: [libs\sql-schema-describer\src\mssql.rs:317:30] called Result::unwrap() on an Err value: "Couldn't parse default value: \r\ncreate default D_BIT_OFF\r\nas 0\r\n"
  • Error: called Result::unwrap() on an Err value: "Couldn't parse default value in SQL Server
  • db pull errors on SQL Server with Error: [libs\sql-schema-describer\src\mssql.rs:336:30] called Result::unwrap()on anErr value: "Couldn't parse default value: [...]
  • Error: [libs\sql-schema-describer\src\mssql.rs:336:30] called Result::unwrap() on an Err value: "Couldn't parse default value: \r\ncreate default [va_nulla] as 0\r\n"
  • Error when pulling from database
  • Foreign key relation results in erroneous second migration
  • db pull can't parse script setting default value
  • Bug: Migrations not compatible with D1
  • SQL Server Introspection crashes on multi-line (deprecated) defaults

  Prisma Client

  • Raw query failed. Code: 22P03. Message: db error: ERROR: incorrect binary data format in bind parameter 1
  • Float number on raw query: incorrect binary data format in bind parameter 1
  • Can't use Prisma client in Next.js middleware, even when deploying to Node.js
  • Prepared statement caching is data dependent on numeric input parameters (incorrect binary data format in bind parameter x)
  • Turso Driver Adapter: Including _count leads to error
  • Next.js app build fails when using Prisma with DB driver in Server Action
  • Bug: [D1] Error in performIO: Error: D1_ERROR: too many SQL variables
  • Remove warn(prisma-client) This is the 10th instance of Prisma Client being started. warning in Edge (and potentially) other envs)
  • $executeRawUnsafe: incorrect binary data format in bind parameter 6
  • Bug: Error or bug using Prisma with DriverAdapter with PostgreSQL database Neon
  • Inconsistent column data: Unexpected conversion failure from Number to BigInt error when using @prisma/adapter-pg
  • Incompatibility with NextJS app dir, CloudFlare Pages and D1
  • Breaking change? Int switched to being Int32 for MongoDB

  Language tools (e.g. VS Code)

  • VS Code extension is showing an advertisement
  • Generate codelens fails on Windows
  • We incorrectly read commented out preview features if they are before the real preview features

  Credits

  Huge thanks to @ pranayat, @ yubrot, and @ skyzh for helping!

• 5.15.0-integration-static-wasm-worker-loader.2 - 2024-05-23
• 5.15.0-integration-static-wasm-worker-loader.1 - 2024-05-22
• 5.15.0-integration-pr-24186.1 - 2024-05-15
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.8 - 2024-06-03
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.7 - 2024-05-31
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.5 - 2024-05-22
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.4 - 2024-05-22
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.3 - 2024-05-22
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.2 - 2024-05-22
• 5.15.0-integration-fix-sqlite-d1-max-bind-values.1 - 2024-05-20
• 5.15.0-integration-feat-cli-pdp-optimize-tracking.1 - 2024-05-14
• 5.15.0-integration-engines-5-15-0-9-wasm-update-nightly-f2a9d342d78503d7a478faefd4bb8a7e79d927f5.1 - 2024-05-27
• 5.15.0-integration-engines-5-15-0-4-integration-fix-sqlite-d1-migrations-93d288241fddb3768c310aeceb6b0120145c6f6d.2 - 2024-05-16
• 5.15.0-integration-engines-5-15-0-4-integration-fix-sqlite-d1-migrations-93d288241fddb3768c310aeceb6b0120145c6f6d.1 - 2024-05-16
• 5.15.0-integration-engines-5-15-0-21-feat-multi-file-introspection-cli-2-146af78f10dc7146469ce4d409ecaca820e74472.1 - 2024-05-30
• 5.15.0-integration-engines-5-15-0-18-feat-multi-file-introspection-cli-2-2161c3dd5f60d5d52f89724118f4b1328f7d161d.1 - 2024-05-30
• 5.15.0-integration-engines-5-15-0-17-feat-multi-file-introspection-cli-1-27cfda7ab7d009c56e2bfb58badc16a348cbeefa.1 - 2024-05-29
• 5.15.0-integration-engines-5-15-0-15-get-config-fault-tolerant-49eaa97e1de2cace3bd0d8016b165ad0012b7f1a.1 - 2024-05-29
• 5.15.0-integration-engines-5-15-0-14-feat-restore-json-noparse-9e8157b12aa689561bf138f5e305ef24cf4bd2e3.1 - 2024-05-29
• 5.15.0-integration-engines-5-15-0-11-integration-fix-sqlite-d1-migrations-9cebc28b8d3cb5e1ebd8ad8d096e1cef4725d5ad.2 - 2024-05-28
• 5.15.0-integration-engines-5-15-0-11-integration-fix-sqlite-d1-migrations-9cebc28b8d3cb5e1ebd8ad8d096e1cef4725d5ad.1 - 2024-05-28
• 5.15.0-integration-client-dynamic-wasm-imports.2 - 2024-05-29
• 5.15.0-integration-client-dynamic-wasm-imports.1 - 2024-05-28
• 5.15.0-dev.73 - 2024-06-04
• 5.15.0-dev.72 - 2024-06-03
• 5.15.0-dev.71 - 2024-06-03
• 5.15.0-dev.70 - 2024-06-03
• 5.15.0-dev.69 - 2024-06-03
• 5.15.0-dev.68 - 2024-06-03
• 5.15.0-dev.67 - 2024-06-03
• 5.15.0-dev.66 - 2024-06-03
• 5.15.0-dev.64 - 2024-06-03
• 5.15.0-dev.63 - 2024-05-31
• 5.15.0-dev.62 - 2024-05-31
• 5.15.0-dev.61 - 2024-05-31
• 5.15.0-dev.60 - 2024-05-31
• 5.15.0-dev.59 - 2024-05-31
• 5.15.0-dev.58 - 2024-05-31
• 5.15.0-dev.57 - 2024-05-31
• 5.15.0-dev.56 - 2024-05-30
• 5.15.0-dev.55 - 2024-05-30
• 5.15.0-dev.54 - 2024-05-30
• 5.15.0-dev.53 - 2024-05-30
• 5.15.0-dev.52 - 2024-05-30
• 5.15.0-dev.51 - 2024-05-30
• 5.15.0-dev.50 - 2024-05-30
• 5.15.0-dev.49 - 2024-05-29
• 5.15.0-dev.48 - 2024-05-29
• 5.15.0-dev.47 - 2024-05-29
• 5.15.0-dev.46 - 2024-05-29
• 5.15.0-dev.45 - 2024-05-29
• 5.15.0-dev.44 - 2024-05-29
• 5.15.0-dev.43 - 2024-05-29
• 5.15.0-dev.42 - 2024-05-29
• 5.15.0-dev.41 - 2024-05-28
• 5.15.0-dev.40 - 2024-05-28
• 5.15.0-dev.39 - 2024-05-28
• 5.15.0-dev.38 - 2024-05-28
• 5.15.0-dev.37 - 2024-05-28
• 5.15.0-dev.36 - 2024-05-28
• 5.15.0-dev.35 - 2024-05-28
• 5.15.0-dev.34 - 2024-05-28
• 5.15.0-dev.33 - 2024-05-27
• 5.15.0-dev.32 - 2024-05-27
• 5.15.0-dev.31 - 2024-05-27
• 5.15.0-dev.30 - 2024-05-23
• 5.15.0-dev.29 - 2024-05-23
• 5.15.0-dev.28 - 2024-05-22
• 5.15.0-dev.27 - 2024-05-22
• 5.15.0-dev.26 - 2024-05-22
• 5.15.0-dev.25 - 2024-05-22
• 5.15.0-dev.24 - 2024-05-22
• 5.15.0-dev.23 - 2024-05-22
• 5.15.0-dev.22 - 2024-05-22
• 5.15.0-dev.21 - 2024-05-22
• 5.15.0-dev.20 - 2024-05-21
• 5.15.0-dev.19 - 2024-05-21
• 5.15.0-dev.18 - 2024-05-21
• 5.15.0-dev.17 - 2024-05-17
• 5.15.0-dev.16 - 2024-05-17
• 5.15.0-dev.15 - 2024-05-16
• 5.15.0-dev.14 - 2024-05-16
• 5.15.0-dev.13 - 2024-05-16
• 5.15.0-dev.12 - 2024-05-15
• 5.15.0-dev.11 - 2024-05-15
• 5.15.0-dev.10 - 2024-05-15
• 5.15.0-dev.9 - 2024-05-15
• 5.15.0-dev.8 - 2024-05-15
• 5.15.0-dev.7 - 2024-05-15
• 5.15.0-dev.6 - 2024-05-15
• 5.15.0-dev.5 - 2024-05-15
• 5.15.0-dev.4 - 2024-05-15
• 5.15.0-dev.3 - 2024-05-15
• 5.15.0-dev.2 - 2024-05-14
• 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!

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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
pokedex-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 27, 2024 8:02am