Prisma

Today, we are issuing the `4.10.1` patch release.

Fixes in Prisma Client

- [Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)](https://github.com/prisma/prisma/issues/17810)
- [4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.](https://github.com/prisma/prisma/issues/17797)

🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20prisma%20release%20v4.10.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.10.0) about the release.** 🌟

Highlights

Improved CLI support for connection poolers

When working with connection poolers such as the [Prisma Data Proxy](https://www.prisma.io/data-platform/proxy), [Accelerate](https://www.prisma.io/data-platform/accelerate) or [pgBouncer](https://www.prisma.io/docs/guides/performance-and-optimization/connection-management/configure-pg-bouncer), it is necessary to use a different URL to connect to the database when using Prisma Client and Prisma Migrate.

We're introducing a new datasource property `directUrl` to improve this. When the `directUrl` property is present, the Prisma CLI will use it to connect to the database for tasks such as introspection and migrations.

sh
.env
Connection to Prisma Data Proxy. Used by Prisma Client.
DATABASE_URL="prisma://__HOST__/?api_key=__KEY__"
Connection to the database. Used for migrations and introspection.
DIRECT_URL="postgresql://__USER__:__PASSWORD____HOST__:__PORT__/__DATABASE__"


prisma
// ./prisma/schema.prisma
generator client {
provider = "prisma-client-js"
}

datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
directUrl = env("DIRECT_URL")
}


To learn more, refer to our [documentation](https://www.prisma.io/docs/data-platform/data-proxy/prisma-cli-with-data-proxy).

Introspection support for PostgreSQL views

We introduced initial support for database views in [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0) with the addition of the `view` keyword. This release introduces introspection support for PostgreSQL views. You can run `prisma db pull` against your database to populate your Prisma schema with your views.

To learn more, refer to our documentation on [views introspection](https://www.prisma.io/docs/concepts/components/prisma-schema/views#use-introspection). Try it out and let us know your thoughts in this [GitHub issue](https://github.com/prisma/prisma/issues/17335).

Improved introspection for unsupported database functionality & partitioned tables

Currently, the Prisma Schema Language(PSL) does not cover the full feature sets of different database providers. For the unsupported database functionality, Prisma provides offers escape hatches like [raw queries](https://www.prisma.io/docs/concepts/components/prisma-client/raw-database-access) or [manual editing of the migration files](https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/customizing-migrations).

While we work on adding support for missing database functionality, e.g. database views, some of it is not fully-supported and the escape hatches fail. Objects that use unsupported properties might not be caught during introspection and raw queries might not work. Re-introspection may sometimes remove the information from the schema file and the generated migrations may be invalid or re-generate the same SQL repeatedly.

We're therefore fixing the defects and supporting the unsupported database functionalities Prisma currently doesn't support. We created a list of these features in [this GitHub issue](https://github.com/prisma/prisma/issues/16311) we would like to improve.

This release improves introspection support for **partitioned tables** in PostgreSQL and MySQL. Previously, Prisma would pick up the partitions as `model`s and miss the _actual_ main table. Prisma will now pick up the main table as a `model`, not the partitions.

If you're already using partitioned tables in your database, you can use `prisma db pull` to update your Prisma schema. If you're already using Prisma and want to partition a table in your database, you can:
1. Create a draft migration using `prisma migrate dev --create-only`
1. Update the draft migration with the SQL to partition the tables
1. Re-run `prisma migrate dev` to apply the draft migration to your database

Try it out and let us know what you think. If you run into an issue, feel free to create a [bug report](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&template=bug_report.yml).

Smaller engine size used in Prisma CLI

In 4.8.0, we decreased the size of the engines by ~50%, which significantly impacted Prisma Client, especially in serverless environments.

In this release, we've reduced the size of Prisma CLI by removing the Introspection and Formatter engines. The introspection functionality is now served by the Migration Engine. A cross-platform Wasm module has entirely replaced the Formatter Engine. This reduces the overall installation size for Prisma CLI.

Fixes and improvements

Prisma Client

- [Precompiled engine files for `aarch64-unknown-linux-musl` target (Alpine Linux on ARM, e.g. M1)](https://github.com/prisma/prisma/issues/8478)
- [Specify the generator to use for sharing schema files in different environments](https://github.com/prisma/prisma/issues/10527)
- [Implement `getDmmf` as Wasm module that could be used in Prisma CLI](https://github.com/prisma/prisma/issues/12482)
- [Client in interactive transaction is not extended ](https://github.com/prisma/prisma/issues/16582)
- [Deeply nested objects aren't typed when clientExtensions is enabled](https://github.com/prisma/prisma/issues/17349)
- [Typescript issue on nested queries with clientExtensions feature](https://github.com/prisma/prisma/issues/17563)

Prisma

- [Introspection can't get composite primary key for partitioned table](https://github.com/prisma/prisma/issues/10870)
- [db pull adds redundant comment about ignored table](https://github.com/prisma/prisma/issues/16796)
- [Remove `prisma-fmt` formatter binary](https://github.com/prisma/prisma/issues/16924)
- [Diagnostics currently need to be manually written for Code Action tests](https://github.com/prisma/prisma/issues/16944)
- [OpenSSL on Node Alpine still not working after Prisma 4.8.0 on an ARM machine](https://github.com/prisma/prisma/issues/16963)
- [Improved error messages on system library detection](https://github.com/prisma/prisma/issues/16970)
- [Remove `introspection-engine` binary from CLI](https://github.com/prisma/prisma/issues/17300)
- [[Stopgap] Introspect partitioned tables better: Only introspect main table in a valid way, ignore partitions](https://github.com/prisma/prisma/issues/17351)
- [Regression: `get-platform` error for non-`amd64` Alpine introduced in `prisma4.9.0` prevents using custom Prisma engines](https://github.com/prisma/prisma/issues/17390)
- [Introspection of PostgreSQL views](https://github.com/prisma/prisma/issues/17413)
- [internal: use original distro and distro family in warning messages](https://github.com/prisma/prisma/issues/17480)
- [Failed to detect linux distro + `Error: Unknown binaryTarget debian-openssl-0.0.x and no custom engine files were provided` after upgrading from 4.8.1 to 4.9.0](https://github.com/prisma/prisma/issues/17499)

Language tools (e.g. VS Code)

- [Add VS Code quick fix / code action to phase out `referentialIntegrity` in favor of `relationMode`](https://github.com/prisma/language-tools/issues/1276)
- [Auto completion of `directUrl`](https://github.com/prisma/language-tools/issues/1359)


Credits

Huge thanks to rintaun, ivan, Mini256, yukukotani, sandrewTx08 for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) live stream.

The stream takes place [on YouTube](https://youtu.be/bLC7sS-9x20) on **Thursday, February 9** at **5 pm Berlin | 8 am San Francisco**.

🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20prisma%20release%20v4.9.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.9.0) about the release.** 🌟

Highlights

Initial support for database views (Preview)

This release introduces a new keyword, `view`, behind the `views` [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) feature flag. You can manually add a `view` to your Prisma schema, which is ignored when running migrations. This is a small step forward but should already be helpful to many of you depending on workarounds and shell scripts to work with views and Migrate.

Here is an example usage of `views`:

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

view UserInfo {
id Int id
// from the User model
email String
name String
// from the Profile model
bio String
}

model User {
id Int id default(autoincrement())
email String unique
name String?
profile Profile?
}

model Profile {
id Int id default(autoincrement())
bio String
user User relation(fields: [userId], references: [id])
userId Int unique
}


To learn more, head to our [documentation](https://prisma.io/docs/concepts/components/prisma-schema/views). Try it out and let us know your thoughts on this [GitHub issue](https://github.com/prisma/prisma/issues/17335).

Multi-schema support for SQL Server (Preview)

We're thrilled to share that this release adds Preview support for multi-schema for SQL Server.

This release adds support for:
- Introspecting databases that organize objects in multiple database schemas
- Managing multi-schema database setups directly from Prisma schema
- Generating migrations that are database schema-aware with Prisma Migrate
- Querying across multiple database schemas with Prisma Client

If you already have a SQL Server database using multiple schemas, you can quickly get up and running and set up multiple schemas by:
- Enabling the Preview feature in the Prisma schema
- Defining the schemas in the `schemas` property in the `datasource` block
- Introspecting your database using `prisma db pull`

You can further evolve your database schema using the multi-schema Preview feature by using `prisma migrate dev`.

For further details, refer to our [documentation](https://prisma.io/docs/guides/database/multi-schema) and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/15077).

Prisma Client Extensions improvements

In this release, we've made a number of improvements to the Prisma Client Extensions Preview feature:

1. Retrieving the current model name at runtime
You can now get the name of the current model at runtime using `Prisma.getExtensionContext(this).name`. You might use this to write out the model name to a log, to send the name to another service, or to branch your code based on the model. You can learn more about this in our [docs](https://www.prisma.io/docs/concepts/components/prisma-client/client-extensions/model#get-the-current-model-name-at-runtime).

1. Improved type safety when defining custom model methods
Prisma Client now provides a set of type utilities that tap into input and output types. They are fully dynamic, which means they adapt to any given model and schema. You can use them to improve your custom model methods' auto-completion. This is especially useful in shared extensions. Learn more about this in our [docs](https://www.prisma.io/docs/concepts/components/prisma-client/client-extensions/model#advanced-type-safety-improve-the-type-safety-and-developer-experience-of-your-custom-model-methods).


Let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/16500) and in case you run into any issues, please create a [bug report](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml).

Introspection and Migration engine improvements

In this release, we moved the Introspection Engine (responsible for `prisma db pull`) which the Migration Engine will now serve. Previously, the Introspection Engine was stand-alone.

Let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/17341) and in case you run into any issues, please create a [bug report](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml).

MongoDB `WriteConflict` bug fix

This version also comes with a notable bug fix: In our MongoDB provider, any queries that are returned with a `WriteConflict` error Prisma now will retry the query, similar to how other MongoDB drivers and clients do.

Prisma plugin for JetBrains IDEs

If you are using a JetBrains IDE the team over at JetBrains recently released an [official Prisma plugin in their Plugin Marketplace](https://plugins.jetbrains.com/plugin/20686-prisma-orm).

Thank you, JetBrains, for working on this! Next to our [VS Code extension for Prisma](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) and our [general language server, which works in many editors](https://www.prisma.io/docs/guides/development-environment/editor-setup), most relevant editors should now be covered.

Accelerate (Early Access)

We’re thrilled to announce Early Access to [Accelerate](https://www.prisma.io/blog/announcing-accelerate-usrvpi6sfkv4).

Accelerate is a global database cache. It is available in 280 locations and has built-in connection pooling for serverless apps. You can make your queries up to 1000 times faster on any Prisma-supported database, reducing your query response times.

Join the waiting list for Accelerate [here](https://prisma103696.typeform.com/to/WwPDKEQ5).

Fixes and improvements

Prisma

- [Feature Request: Jetbrains (IntelliJ IDEA, Webstorm) Plugin](https://github.com/prisma/prisma/issues/1788)
- [Misleading 'We need to reset the PostgreSQL database' when using PostgreSQL _schemas_](https://github.com/prisma/prisma/issues/10043)
- [Solve "P1012 Introspection failed" errors on Windows CI](https://github.com/prisma/prisma/issues/13077)
- [support NanoID](https://github.com/prisma/prisma/issues/14004)
- [Create CI worker without a proper `openssl` or `libc` installation to improve snapshot testing suite](https://github.com/prisma/prisma/issues/14017)
- [db pull --url with an invalid url produces a misleading error message](https://github.com/prisma/prisma/issues/14732)
- [(re)-Introspection errors have a misleading error message](https://github.com/prisma/prisma/issues/16176)
- [multi-schema + introspection: rename models and enums to avoid name collisions](https://github.com/prisma/prisma/issues/16454)
- [multiSchema + introspection: add `--schemas` param to the `db pull` command](https://github.com/prisma/prisma/issues/16455)
- [Cross schema reference with foreign key not working in 4.7.0+](https://github.com/prisma/prisma/issues/16585)
- [Handle missing `schemas` property different when cross schema references are detected (when `multiSchema` preview feature is enabled)](https://github.com/prisma/prisma/issues/16615)
- [`db pull` with `multiSchema` enabled and `schemas` defined, outputs `public` in CLI message anyway](https://github.com/prisma/prisma/issues/16635)
- [Remove DML dependency from MongoDB introspection](https://github.com/prisma/prisma/issues/16894)
- [I want short unique id. UUID, CUID are too long](https://github.com/prisma/prisma/issues/16914)
- [Completions: for `schemas` property in `datasource`](https://github.com/prisma/prisma/issues/16920)
- [Completions `schema` attribute](https://github.com/prisma/prisma/issues/16957)
- [OS Support: improve SSL detection on `debian` distros](https://github.com/prisma/prisma/issues/16962)
- [`multiSchema`: add `schemas` property to `getConfig` output](https://github.com/prisma/prisma/issues/17031)
- [multiSchema: `migrate reset` with sqlserver does not delete second schema](https://github.com/prisma/prisma/issues/17051)
- [Prisma 4.9.x (dev version) broke `openssl` detection for Linux distros besides Alpine and Debian-based distros, like RHEL](https://github.com/prisma/prisma/issues/17063)
- [Wrong db pull warning with multiSchema preview feature, it says that `These enums were enriched with `map` information taken from the previous Prisma schema.` but the schema file datamodel is actually empty.](https://github.com/prisma/prisma/issues/17095)
- [PSL: Recognize the `view` keyword](https://github.com/prisma/prisma/issues/17115)
- [ previewFeatures = ["multiSchema"] Error when doing db pull](https://github.com/prisma/prisma/issues/17176)
- [17126 broke the `platform-serverless-vercel/vercel-cli` ecosystem tests](https://github.com/prisma/prisma/issues/17264)
- [When `distro` is undefined, the output of `ldconfig` is ignored because of the `sed: -e expression 1, char 7: unknown option to `s'` silent error](https://github.com/prisma/prisma/issues/17321)

Prisma Client

- [Detect absense of openssl and inform the user about it](https://github.com/prisma/prisma/issues/6211)
- [prisma4.7.1 - "RangeError: Maximum call stack size exceeded" when clientExtensions enabled](https://github.com/prisma/prisma/issues/16600)
- [Prisma 4.8 produces conflicting typescript types for custom many to many relations](https://github.com/prisma/prisma/issues/17005)
- [Using findUnique on 4.8.0 with nested `where` and `include` produces an object that doesn't include entities you specify in `include`](https://github.com/prisma/prisma/issues/17030)
- [Error: Maximum call stack size exceeded is thrown after I used clientExtensions as preview feature.](https://github.com/prisma/prisma/issues/17236)
- [MongoDB: Using `delete` on a one-to-one relation while updating removes other relations](https://github.com/prisma/prisma/issues/17255)
- [Promise types are not unwrapped properly when using async/await in WebStorm](https://github.com/prisma/prisma/issues/17266)
- [Deeply nested objects aren't typed when clientExtensions is enabled](https://github.com/prisma/prisma/issues/17349)

Prisma Migrate

- [migrations: Ignore view definitions](https://github.com/prisma/prisma/issues/17117)
- [Migrate dev breaks on multiSchema with SQL Server](https://github.com/prisma/prisma/issues/17220)

Language tools (e.g. VS Code)

- [Improve local development workflow and update documentation](https://github.com/prisma/language-tools/issues/961)
- [Integer.MAX_VALUE is not portable across clients](https://github.com/prisma/language-tools/issues/1086)
- [Quick Fix: add `schema` attribute to model / enum](https://github.com/prisma/language-tools/issues/1329)
- [Completions: from the list of available schema namespaces](https://github.com/prisma/language-tools/issues/1332)
- [Recognizing the `view` keyword](https://github.com/prisma/language-tools/issues/1346)

Prisma Engines

- [update napi dependencies from `2.9.1` to `2.10.1`](https://github.com/prisma/prisma-engines/issues/3521)
- [me/ie rewiring: add `introspect` tests to `migration-engine`](https://github.com/prisma/prisma-engines/issues/3559)

Credits

Huge thanks rintaun, ivan, Mini256, fubhy, unflxw, Mosaab-Emam for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) live stream.

The stream takes place [on YouTube](https://youtu.be/A6AbeZF4cUY) on **Thursday, January 26** at **5 pm Berlin | 8 am San Francisco**.

Today, we are issuing the `4.8.1` patch release.

Fix in Prisma Client

- [Prisma 4.8 produces conflicting typescript types for custom many to many relations](https://github.com/prisma/prisma/issues/17005)

🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20prisma%20release%20v4.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.8.0) about the release.** 🌟

Highlights

Improved serverless experience — smaller engines size

In this release, we have decreased the size of our engine files by an average of 50%. The size of the Query Engine used on Debian, with OpenSSL 3.0.x, for example, went from 39MB to 14MB. We will also remove some smaller engines to decrease the total size in future versions.

Additionally, we have started optimizing how the Prisma schema is loaded in Prisma Client. You should notice a considerable improvement when executing the first query if you're working with a bigger schema with many models and relations.

We will continue investing in this direction in the next releases and further improve the experience with Prisma and serverless environments.

Multi-schema support for CockroachDB (Preview)

We're pleased to share that this release adds [Preview support](https://www.prisma.io/docs/about/prisma/releases#preview) for multi-schema for CockroachDB. 🎉

This release adds support for:
- Introspecting databases that organize objects in multiple database schemas
- Managing multi-schema database setups directly from Prisma schema
- Generating migrations that are database schema-aware with Prisma Migrate
- Querying across multiple database schemas with Prisma Client

If you already have a CockroachDB database using multiple schemas, you can quickly get up and running set up multiple schemas by:
- Enabling the Preview feature in the Prisma schema
- Defining the schemas in the `schemas` property in the `datasource` block
- Introspecting your database using `prisma db pull`

You can further evolve your database schema using the multi-schema Preview feature by using `prisma migrate dev`.

For further details, refer to our [documentation](https://prisma.io/docs/guides/database/multi-schema) and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/15077).

Improved OpenSSL 3.x support

Prisma now supports OpenSSL 3 builds for Linux Alpine on `x86_64` architectures. This particularly impacts users running Prisma on `node:alpine` and `node:lts-alpine` Docker images. The images are based on an Alpine version that ships with OpenSSL 3.0.x, which isn’t compatible with OpenSSL 1.1.x (already supported by Prisma). You can read more details about it in this GitHub [comment](https://github.com/prisma/prisma/issues/16553#issuecomment-1353302617).

We also have rewritten our OpenSSL version detection logic, making it future-proof. We now expect Prisma to support systems running with any OpenSSL 3 minor versions out of the box.

Fixes and improvements

Prisma

- [Migrate: dbgenerated with db.Time(0) keeps generating new migrations](https://github.com/prisma/prisma/issues/6382)
- [Error parsing attribute "index": The Gin index field type `Uuid` has no default operator class.](https://github.com/prisma/prisma/issues/14587)
- [UTF-8 Error: index is not a char boundary](https://github.com/prisma/prisma/issues/14895)
- [Error in migration engine. Reason: entered unreachable code ](https://github.com/prisma/prisma/issues/16340)
- [Regression in enum default value handling in 4.7.0](https://github.com/prisma/prisma/issues/16546)
- [Regression in relation field name deduplication](https://github.com/prisma/prisma/issues/16547)
- [multiSchema: `migrate reset` only resets first schema](https://github.com/prisma/prisma/issues/16561)
- [Cross schema reference with foreign key not working in 4.7.0. ](https://github.com/prisma/prisma/issues/16585)
- [Support SQL Server in `multiSchema` introspection](https://github.com/prisma/prisma/issues/16627)
- [`migrate dev` does not detect drift between database schema and migration history for `multiSchema`](https://github.com/prisma/prisma/issues/16634)
- [Bad credentials when downloading using prisma/fetch-engines](https://github.com/prisma/prisma/issues/16685)
- [multiSchema: migrate dev fails to apply cleanly to shadow database after custom migration renames table in secondary schema](https://github.com/prisma/prisma/issues/16794)

Prisma Migrate

- [Prisma db migration always altering my table contains mysql TIME data type inside of it](https://github.com/prisma/prisma/issues/9769)
- [Prisma migration fails with postgres](https://github.com/prisma/prisma/issues/15826)
- [Migrate Dev CMD Issue when using `multiSchema` preview feature with MySQL](https://github.com/prisma/prisma/issues/16274)

Prisma Client

- [Prisma 4.3.1 distribution is bundling a libquery_engine](https://github.com/prisma/prisma/issues/15244)
- [enum fields are missing in select's type when `clientExtensions` preview feature is used](https://github.com/prisma/prisma/issues/16535)
- [`$extends` TS error: "Inferred type of this node exceeds the maximum length the compiler will serialize" with `"declaration": true` in `tsconfig`](https://github.com/prisma/prisma/issues/16536)
- [Regression bug: batched findUniqueOrThrow queries throw 'Field does not exist on enclosing type.'](https://github.com/prisma/prisma/issues/16548)
- [Prisma Client Extensions: `args` is `undefined`](https://github.com/prisma/prisma/issues/16551)
- [Support OpenSSL 3.0 for Alpine Linux](https://github.com/prisma/prisma/issues/16553)
- [`console.log` outputs incorrect value when `result` extensions are used](https://github.com/prisma/prisma/issues/16554)
- [4.6.0 and newer does not let me spy using vitest.](https://github.com/prisma/prisma/issues/16584)
- [Investigate memory issues on Windows](https://github.com/prisma/prisma/issues/16594)
- [prisma4.7.1 - "RangeError: Maximum call stack size exceeded" when clientExtensions enabled](https://github.com/prisma/prisma/issues/16600)
- [Unique constraint error when connecting an item in a 1-1 relation that is already connected](https://github.com/prisma/prisma/issues/16743)
- [Error when using "multiSchema" with custom database schema and implicit Many To Many relation](https://github.com/prisma/prisma/issues/16761)
- [binaries.prisma.sh not accessible via IPv6](https://github.com/prisma/prisma/issues/16777)
- [Nested disconnect fails with `extendedWhereUnique` on SQL](https://github.com/prisma/prisma/issues/16843)

Language tools (e.g. VS Code)

- [Auto completion suggests `map` although already present](https://github.com/prisma/language-tools/issues/1079)
- [Update message for detecting both Stable and Insiders in workspace](https://github.com/prisma/language-tools/issues/1315)
- [Update to use correct form of criteri(a/on)](https://github.com/prisma/language-tools/issues/1321)
- [Extra `'` in optional arguments context](https://github.com/prisma/language-tools/issues/1337)

Prisma Engines

- [Use correct forms of "criterion" (singular) and "criteria" (plural)](https://github.com/prisma/prisma-engines/issues/3126)
- [Only use buildjet action runner where needed](https://github.com/prisma/prisma-engines/issues/3370)
- [Bug: `schema` attribute should always be required when `schemas` is defined in the datasource](https://github.com/prisma/prisma-engines/issues/3502)

Credits

Huge thanks to ivan, Mini256, cmd-johnson for helping!

Prisma Help Center (New)

We recently just launched our [Help Center](https://www.prisma.io/support) that you can use to find resources and get help from our support team for both the Prisma ORM and the Prisma Data Platform.

Check it out, and let us know what you think.

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://youtu.be/-0kwU2y0SCA) live stream.

The stream takes place [on YouTube](https://youtu.be/-0kwU2y0SCA) on **Thursday, December 22** at **5 pm Berlin | 8 am San Francisco**.

Today, we are issuing the `4.7.1` patch release.

Fixes in Prisma Client

- [Enum fields are missing in select's type when `clientExtensions` preview feature is used](https://github.com/prisma/prisma/issues/16535)
- [`console.log` outputs incorrect value when `result` extensions are used](https://github.com/prisma/prisma/issues/16554)
- ["Field does not exist on enclosing type" error is thrown in `findUniqueOrThrow`](https://github.com/prisma/prisma/issues/16548)
- [Prisma Client Extensions: `args` is `undefined`](https://github.com/prisma/prisma/issues/16551)