:arrow_up: Bump @prisma/client from 2.14.0 to 4.12.0

[dependabot[bot]]

Bumps @prisma/client from 2.14.0 to 4.12.0.

Release notes

Sourced from @​prisma/client's releases.

4.12.0

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

Highlights

Introspection of Views SQL improvements (Preview)

The views Preview feature significantly improved this release: prisma db pull now reads the SQL query used to define a view and stores it in a .sql file in a views folder next to your Prisma schema.

Note: These .sql files are not yet used for creating or updating views during migrations yet. For now, we are only looking for feedback. Let us know if the introspected SQL files match the views picked up in your database and if the correct files were created in your filesystem.

We encourage you to leave feedback in this GitHub issue.

Improvements to JSON protocol (Early Preview)

In 4.11.0, we announced the jsonProtocol Preview feature which had some rough edges. This release improves the Preview feature by providing polished and helpful error messages from Prisma Client when something goes wrong. Here is an example error message:

We would appreciate it if you would try it out to help us polish the feature and move it to General Availability. Testing it requires little effort. Please also leave any feedback in this issue, or open a new one if you want to report a bug.

Prisma Client startup performance

In this release, we've improved the startup performance of Prisma Client. We're keen on improving the performance of Prisma Client. If you experience any problems with the startup performance, be sure to report them so that we can look into them.

Open Telemetry tracing and logging for Prisma Client for Data Proxy

This release adds support for Open Telemetry tracing (via the tracing Preview feature) and logging to Prisma Client for Data Proxy.

Fixes and improvements

Prisma Migrate

• Certain types of schema changes don't work with CockroachDB v22.2
• Completions: provided by engines break right at the start of a newline
• db pull fail with particular enum default value in column
• Unable to reset CockroachDB for table with foreign key relationship on v22.2.
• Introspection of SQLite views
• Changing the Column Type to Enum on a model throws an error
• Introspection of the view definition statement
• MySQL multi-value index removes the primary key on introspection

Prisma Client

• findUnique used with Promise.all returns null
• Missing PrismaPromise export after update from 4.9.0 to 4.11.0
• jsonProtocol doesn't query enum fields by default
• Prisma 4.11 breaks multilevel relation with compound primary keys (typings)
• 4.11.0: Unique constraint failed on the fields on query that worked in 4.10.1
• jsonProtocol Field/Enum is not included in the result of the findFirst/findMany function

... (truncated)

Commits

• 35abae2 chore(deps): update engines to 4.12.0-67.659ef412370fa3b41cd7bf6e94587c1dfb7f...
• 4c139e5 chore(deps): bump benchmark.js codspeed plugin to 1.0.2 (#18514)
• ba6ea8e fix(client): Correct result for hasOwn/hasOwnProperty on proxies (#18519)
• 5b3ec51 chore(client): Unskip some of the json protocol validation tests (#18511)
• c9e3091 chore(deps): update engines to 4.12.0-64.7d39155bcb3183078ffc3cf9be5d110cc3f9...
• 28665e2 chore(deps): update engines to 4.12.0-63.a85283b72c78fa93051762f899d5f8f5716f...
• 886c1d3 chore(deps): update engines to 4.12.0-62.3dcc3fc6e294befa6ccbe0b3d466cb2f36fd...
• 01b20b8 feat(client): error rendering for JSON protocol (#18421)
• ddc5ed1 chore(deps): update engines to 4.12.0-60.393ad1f4e45b1728c101c20ef9cd5047cee7...
• dbc2bb3 fix(client): Restore non-namespaced PrismaPromise export (#18475)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prismabot, a new releaser for @​prisma/client since your current version.

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)

[dependabot[bot]]

Superseded by #2067.