prisma/prisma
### [`v4.11.0`](https://togithub.com/prisma/prisma/releases/tag/4.11.0)
[Compare Source](https://togithub.com/prisma/prisma/compare/4.10.1...4.11.0)
🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v4.11.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.11.0) about the release.** 🌟
#### Highlights
##### JSON protocol Early Preview
This release introduces an early Preview feature: JSON protocol.
If you have been using Prisma for a while, read our [documentation about our Query Engine](https://www.prisma.io/docs/concepts/components/prisma-engines) or peeked at our codebase, you might be aware that Prisma Client uses a GraphQL-like protocol to communicate to the Query Engine when you execute a query. This was mainly because of historical reasons (Prisma was born initially from the GraphQL backend-as-a-service “Graphcool”) and wasn't changed as it worked well.
During performance investigations and optimizations, though, we noticed that GraphQL added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON.
To try out the new protocol, enable the `jsonProtocol` Preview feature in your Prisma schema:
```prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["jsonProtocol"]
}
```
Regenerate Prisma Client to use the new JSON protocol.
For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: `PRISMA_ENGINE_PROTOCOL=json`.
Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases.
We expect using `jsonProtocol` to improve Prisma Client's startup performance significantly. This will likely have a more significant impact on applications with larger Prisma schemas.
We would appreciate your feedback on this feature on the following particularly:
1. Does using this preview feature introduce any regressions or problems in your application?
2. If not, how does it influence the performance of your application? Can you share before and after measurements?
For feedback, please comment on the [GitHub feedback issue](https://togithub.com/prisma/prisma/issues/18095).
##### Introspection support for MySQL, SQL Server, and CockroachDB views
You can now run `prisma db pull` against your database to populate your Prisma schema with your views in MySQL, SQL Server, and CockroachDB.
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://togithub.com/prisma/prisma/issues/17335).
##### Webpack plugin for Next.js apps using Prisma in monorepo setups
If you've been using Prisma Client in a Next.js app in a monorepo setup, you might have seen this infamous error message:
Error: ENOENT: no such file or directory, open schema.prisma
We finally pinpointed the problem's source to the Next.js bundling step and opened [an issue in the Next.js repository for Vercel to investigate](https://togithub.com/vercel/next.js/issues/46070) and hopefully fix it.
In the meantime, we've created a workaround via a webpack plugin that makes sure your Prisma schema is copied to the correct location: `@prisma/nextjs-monorepo-workaround-plugin`.
To use the plugin, first install it:
npm install -D @prisma/nextjs-monorepo-workaround-plugin
Import the plugin into your `next.config.js` file and use it in `config.plugins`:
```js
const { PrismaPlugin } = require('@prisma/nextjs-monorepo-workaround-plugin')
module.exports = {
webpack: (config, { isServer }) => {
if (isServer) {
config.plugins = [...config.plugins, new PrismaPlugin()]
}
return config
},
}
```
For further information, refer to our [documentation](https://www.prisma.io/docs/guides/database/troubleshooting-orm/help-articles/nextjs-prisma-client-monorepo) to learn how to use it and [open an issue](https://togithub.com/prisma/prisma/issues/new/choose) if it doesn't work as expected.
#### Fixes and improvements
##### Prisma Client
- [Prisma hangs when javascript is minified](https://togithub.com/prisma/prisma/issues/12355)
- [Issue with prisma failing to locate schema file in monorepo](https://togithub.com/prisma/prisma/issues/12588)
- [NextJS try to open "schema.prisma" at wrong path.](https://togithub.com/prisma/prisma/issues/12823)
- [pnpm workspace + nextjs: `ENOENT: no such file or directory, open '...\.next\server\pages\api\schema.prisma'`](https://togithub.com/prisma/prisma/issues/12853)
- [next.js ENOENT trying to open schema.prisma](https://togithub.com/prisma/prisma/issues/12921)
- [Error with custom output in NPM monorepo: `Error: ENOENT: no such file or directory, open 'schema.prisma'`](https://togithub.com/prisma/prisma/issues/13233)
- [Error with custom output in Turborepo using Blitz.js: Error: ENOENT: no such file or directory, open '<...>/schema.prisma'](https://togithub.com/prisma/prisma/issues/14566)
- [Upsert fails on Postgres with list column.](https://togithub.com/prisma/prisma/issues/16760)
- [Error received when connecting items in an existing one-to-many relationship on MySQL](https://togithub.com/prisma/prisma/issues/17103)
- [`ENOENT` with custom output and ESM module in NPM monorepo (including Nextjs): `no such file or directory, open /.../schema.prisma...`](https://togithub.com/prisma/prisma/issues/17687)
- [Setting `ignoreEnvVarErrors: true` Node API QE causes `datasourceOverrides` to be ignored](https://togithub.com/prisma/prisma/issues/17873)
- [PCE: Support query extensions for raw queries](https://togithub.com/prisma/prisma/issues/18027)
##### Prisma Migrate
- [sslaccept=accept_invalid_certs not working with mysql server 8.0.30](https://togithub.com/prisma/prisma/issues/14903)
- [Error 08S01 (1043) -> Bad Handshake. MySQL Connection with SSL certs](https://togithub.com/prisma/prisma/issues/16886)
- [Introspection of MySQL views](https://togithub.com/prisma/prisma/issues/17414)
- [Introspection of SQL Server views](https://togithub.com/prisma/prisma/issues/17415)
- [Introspection of CockroachDB views](https://togithub.com/prisma/prisma/issues/17418)
- [`db pull`: add new codes for introspection warnings for views in the CLI](https://togithub.com/prisma/prisma/issues/17578)
- [Figure out where getDMMF is used for validation](https://togithub.com/prisma/prisma/issues/17618)
- [Error when `directUrl` is `prisma://` connection string](https://togithub.com/prisma/prisma/issues/17780)
- [4.10.0, unexpected: `errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.`](https://togithub.com/prisma/prisma/issues/17797)
- [Validation output is now always colored, also in CI](https://togithub.com/prisma/prisma/issues/17806)
- [Prisma Client falsely validates `directUrl` env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)](https://togithub.com/prisma/prisma/issues/17810)
- [Fix Postgres introspection of partition tables false positives on inherited tables](https://togithub.com/prisma/prisma/issues/17816)
- [Support openSUSE Tumbleweed](https://togithub.com/prisma/prisma/issues/17947)
- [Change `validate` to return `Result<(), JsError>` in `Wasm` module](https://togithub.com/prisma/prisma/issues/17955)
- [(internal): add unit tests for path-specific libssl version parsing](https://togithub.com/prisma/prisma/issues/18001)
#### Credits
Huge thanks to [@KhooHaoYit](https://togithub.com/KhooHaoYit), [@rintaun](https://togithub.com/rintaun), [@ivan](https://togithub.com/ivan), [@Mini256](https://togithub.com/Mini256), [@Lioness100](https://togithub.com/Lioness100), [@yukukotani](https://togithub.com/yukukotani), [@sandrewTx08](https://togithub.com/sandrewTx08), [@fubhy](https://togithub.com/fubhy), [@zachtil](https://togithub.com/zachtil), [@unflxw](https://togithub.com/unflxw), [@Mosaab-Emam](https://togithub.com/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/-Q5vV6s4jIU) on **Thursday, March 2** at **5 pm Berlin | 8 am San Francisco**.
### [`v4.10.1`](https://togithub.com/prisma/prisma/releases/tag/4.10.1)
[Compare Source](https://togithub.com/prisma/prisma/compare/4.10.0...4.10.1)
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://togithub.com/prisma/prisma/issues/17810)
- [4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.](https://togithub.com/prisma/prisma/issues/17797)
### [`v4.10.0`](https://togithub.com/prisma/prisma/releases/tag/4.10.0)
[Compare Source](https://togithub.com/prisma/prisma/compare/4.9.0...4.10.0)
🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%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://togithub.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://togithub.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://togithub.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`
2. Update the draft migration with the SQL to partition the tables
3. 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://togithub.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://togithub.com/prisma/prisma/issues/8478)
- [Specify the generator to use for sharing schema files in different environments](https://togithub.com/prisma/prisma/issues/10527)
- [Implement `getDmmf` as Wasm module that could be used in Prisma CLI](https://togithub.com/prisma/prisma/issues/12482)
- [Client in interactive transaction is not extended ](https://togithub.com/prisma/prisma/issues/16582)
- [Deeply nested objects aren't typed when clientExtensions is enabled](https://togithub.com/prisma/prisma/issues/17349)
- [Typescript issue on nested queries with clientExtensions feature](https://togithub.com/prisma/prisma/issues/17563)
##### Prisma
- [Introspection can't get composite primary key for partitioned table](https://togithub.com/prisma/prisma/issues/10870)
- [db pull adds redundant comment about ignored table](https://togithub.com/prisma/prisma/issues/16796)
- [Remove `prisma-fmt` formatter binary](https://togithub.com/prisma/prisma/issues/16924)
- [Diagnostics currently need to be manually written for Code Action tests](https://togithub.com/prisma/prisma/issues/16944)
- [OpenSSL on Node Alpine still not working after Prisma 4.8.0 on an ARM machine](https://togithub.com/prisma/prisma/issues/16963)
- [Improved error messages on system library detection](https://togithub.com/prisma/prisma/issues/16970)
- [Remove `introspection-engine` binary from CLI](https://togithub.com/prisma/prisma/issues/17300)
- [\[Stopgap\] Introspect partitioned tables better: Only introspect main table in a valid way, ignore partitions](https://togithub.com/prisma/prisma/issues/17351)
- [Regression: `get-platform` error for non-`amd64` Alpine introduced in `prisma@4.9.0` prevents using custom Prisma engines](https://togithub.com/prisma/prisma/issues/17390)
- [Introspection of PostgreSQL views](https://togithub.com/prisma/prisma/issues/17413)
- [internal: use original distro and distro family in warning messages](https://togithub.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://togithub.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://togithub.com/prisma/language-tools/issues/1276)
- [Auto completion of `directUrl`](https://togithub.com/prisma/language-tools/issues/1359)
#### Credits
Huge thanks to [@rintaun](https://togithub.com/rintaun), [@ivan](https://togithub.com/ivan), [@Mini256](https://togithub.com/Mini256), [@yukukotani](https://togithub.com/yukukotani), [@sandrewTx08](https://togithub.com/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**.
Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
^4.9.0->^4.11.04.9.0->4.11.0Release Notes
prisma/prisma
### [`v4.11.0`](https://togithub.com/prisma/prisma/releases/tag/4.11.0) [Compare Source](https://togithub.com/prisma/prisma/compare/4.10.1...4.11.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v4.11.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.11.0) about the release.** 🌟 #### Highlights ##### JSON protocol Early Preview This release introduces an early Preview feature: JSON protocol. If you have been using Prisma for a while, read our [documentation about our Query Engine](https://www.prisma.io/docs/concepts/components/prisma-engines) or peeked at our codebase, you might be aware that Prisma Client uses a GraphQL-like protocol to communicate to the Query Engine when you execute a query. This was mainly because of historical reasons (Prisma was born initially from the GraphQL backend-as-a-service “Graphcool”) and wasn't changed as it worked well. During performance investigations and optimizations, though, we noticed that GraphQL added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON. To try out the new protocol, enable the `jsonProtocol` Preview feature in your Prisma schema: ```prisma generator client { provider = "prisma-client-js" previewFeatures = ["jsonProtocol"] } ``` Regenerate Prisma Client to use the new JSON protocol. For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: `PRISMA_ENGINE_PROTOCOL=json`. Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases. We expect using `jsonProtocol` to improve Prisma Client's startup performance significantly. This will likely have a more significant impact on applications with larger Prisma schemas. We would appreciate your feedback on this feature on the following particularly: 1. Does using this preview feature introduce any regressions or problems in your application? 2. If not, how does it influence the performance of your application? Can you share before and after measurements? For feedback, please comment on the [GitHub feedback issue](https://togithub.com/prisma/prisma/issues/18095). ##### Introspection support for MySQL, SQL Server, and CockroachDB views You can now run `prisma db pull` against your database to populate your Prisma schema with your views in MySQL, SQL Server, and CockroachDB. 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://togithub.com/prisma/prisma/issues/17335). ##### Webpack plugin for Next.js apps using Prisma in monorepo setups If you've been using Prisma Client in a Next.js app in a monorepo setup, you might have seen this infamous error message: Error: ENOENT: no such file or directory, open schema.prisma We finally pinpointed the problem's source to the Next.js bundling step and opened [an issue in the Next.js repository for Vercel to investigate](https://togithub.com/vercel/next.js/issues/46070) and hopefully fix it. In the meantime, we've created a workaround via a webpack plugin that makes sure your Prisma schema is copied to the correct location: `@prisma/nextjs-monorepo-workaround-plugin`. To use the plugin, first install it: npm install -D @prisma/nextjs-monorepo-workaround-plugin Import the plugin into your `next.config.js` file and use it in `config.plugins`: ```js const { PrismaPlugin } = require('@prisma/nextjs-monorepo-workaround-plugin') module.exports = { webpack: (config, { isServer }) => { if (isServer) { config.plugins = [...config.plugins, new PrismaPlugin()] } return config }, } ``` For further information, refer to our [documentation](https://www.prisma.io/docs/guides/database/troubleshooting-orm/help-articles/nextjs-prisma-client-monorepo) to learn how to use it and [open an issue](https://togithub.com/prisma/prisma/issues/new/choose) if it doesn't work as expected. #### Fixes and improvements ##### Prisma Client - [Prisma hangs when javascript is minified](https://togithub.com/prisma/prisma/issues/12355) - [Issue with prisma failing to locate schema file in monorepo](https://togithub.com/prisma/prisma/issues/12588) - [NextJS try to open "schema.prisma" at wrong path.](https://togithub.com/prisma/prisma/issues/12823) - [pnpm workspace + nextjs: `ENOENT: no such file or directory, open '...\.next\server\pages\api\schema.prisma'`](https://togithub.com/prisma/prisma/issues/12853) - [next.js ENOENT trying to open schema.prisma](https://togithub.com/prisma/prisma/issues/12921) - [Error with custom output in NPM monorepo: `Error: ENOENT: no such file or directory, open 'schema.prisma'`](https://togithub.com/prisma/prisma/issues/13233) - [Error with custom output in Turborepo using Blitz.js: Error: ENOENT: no such file or directory, open '<...>/schema.prisma'](https://togithub.com/prisma/prisma/issues/14566) - [Upsert fails on Postgres with list column.](https://togithub.com/prisma/prisma/issues/16760) - [Error received when connecting items in an existing one-to-many relationship on MySQL](https://togithub.com/prisma/prisma/issues/17103) - [`ENOENT` with custom output and ESM module in NPM monorepo (including Nextjs): `no such file or directory, open /.../schema.prisma...`](https://togithub.com/prisma/prisma/issues/17687) - [Setting `ignoreEnvVarErrors: true` Node API QE causes `datasourceOverrides` to be ignored](https://togithub.com/prisma/prisma/issues/17873) - [PCE: Support query extensions for raw queries](https://togithub.com/prisma/prisma/issues/18027) ##### Prisma Migrate - [sslaccept=accept_invalid_certs not working with mysql server 8.0.30](https://togithub.com/prisma/prisma/issues/14903) - [Error 08S01 (1043) -> Bad Handshake. MySQL Connection with SSL certs](https://togithub.com/prisma/prisma/issues/16886) - [Introspection of MySQL views](https://togithub.com/prisma/prisma/issues/17414) - [Introspection of SQL Server views](https://togithub.com/prisma/prisma/issues/17415) - [Introspection of CockroachDB views](https://togithub.com/prisma/prisma/issues/17418) - [`db pull`: add new codes for introspection warnings for views in the CLI](https://togithub.com/prisma/prisma/issues/17578) - [Figure out where getDMMF is used for validation](https://togithub.com/prisma/prisma/issues/17618) - [Error when `directUrl` is `prisma://` connection string](https://togithub.com/prisma/prisma/issues/17780) - [4.10.0, unexpected: `errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.`](https://togithub.com/prisma/prisma/issues/17797) - [Validation output is now always colored, also in CI](https://togithub.com/prisma/prisma/issues/17806) - [Prisma Client falsely validates `directUrl` env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)](https://togithub.com/prisma/prisma/issues/17810) - [Fix Postgres introspection of partition tables false positives on inherited tables](https://togithub.com/prisma/prisma/issues/17816) - [Support openSUSE Tumbleweed](https://togithub.com/prisma/prisma/issues/17947) - [Change `validate` to return `Result<(), JsError>` in `Wasm` module](https://togithub.com/prisma/prisma/issues/17955) - [(internal): add unit tests for path-specific libssl version parsing](https://togithub.com/prisma/prisma/issues/18001) #### Credits Huge thanks to [@KhooHaoYit](https://togithub.com/KhooHaoYit), [@rintaun](https://togithub.com/rintaun), [@ivan](https://togithub.com/ivan), [@Mini256](https://togithub.com/Mini256), [@Lioness100](https://togithub.com/Lioness100), [@yukukotani](https://togithub.com/yukukotani), [@sandrewTx08](https://togithub.com/sandrewTx08), [@fubhy](https://togithub.com/fubhy), [@zachtil](https://togithub.com/zachtil), [@unflxw](https://togithub.com/unflxw), [@Mosaab-Emam](https://togithub.com/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/-Q5vV6s4jIU) on **Thursday, March 2** at **5 pm Berlin | 8 am San Francisco**. ### [`v4.10.1`](https://togithub.com/prisma/prisma/releases/tag/4.10.1) [Compare Source](https://togithub.com/prisma/prisma/compare/4.10.0...4.10.1) 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://togithub.com/prisma/prisma/issues/17810) - [4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.](https://togithub.com/prisma/prisma/issues/17797) ### [`v4.10.0`](https://togithub.com/prisma/prisma/releases/tag/4.10.0) [Compare Source](https://togithub.com/prisma/prisma/compare/4.9.0...4.10.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%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://togithub.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://togithub.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://togithub.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` 2. Update the draft migration with the SQL to partition the tables 3. 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://togithub.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://togithub.com/prisma/prisma/issues/8478) - [Specify the generator to use for sharing schema files in different environments](https://togithub.com/prisma/prisma/issues/10527) - [Implement `getDmmf` as Wasm module that could be used in Prisma CLI](https://togithub.com/prisma/prisma/issues/12482) - [Client in interactive transaction is not extended ](https://togithub.com/prisma/prisma/issues/16582) - [Deeply nested objects aren't typed when clientExtensions is enabled](https://togithub.com/prisma/prisma/issues/17349) - [Typescript issue on nested queries with clientExtensions feature](https://togithub.com/prisma/prisma/issues/17563) ##### Prisma - [Introspection can't get composite primary key for partitioned table](https://togithub.com/prisma/prisma/issues/10870) - [db pull adds redundant comment about ignored table](https://togithub.com/prisma/prisma/issues/16796) - [Remove `prisma-fmt` formatter binary](https://togithub.com/prisma/prisma/issues/16924) - [Diagnostics currently need to be manually written for Code Action tests](https://togithub.com/prisma/prisma/issues/16944) - [OpenSSL on Node Alpine still not working after Prisma 4.8.0 on an ARM machine](https://togithub.com/prisma/prisma/issues/16963) - [Improved error messages on system library detection](https://togithub.com/prisma/prisma/issues/16970) - [Remove `introspection-engine` binary from CLI](https://togithub.com/prisma/prisma/issues/17300) - [\[Stopgap\] Introspect partitioned tables better: Only introspect main table in a valid way, ignore partitions](https://togithub.com/prisma/prisma/issues/17351) - [Regression: `get-platform` error for non-`amd64` Alpine introduced in `prisma@4.9.0` prevents using custom Prisma engines](https://togithub.com/prisma/prisma/issues/17390) - [Introspection of PostgreSQL views](https://togithub.com/prisma/prisma/issues/17413) - [internal: use original distro and distro family in warning messages](https://togithub.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://togithub.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://togithub.com/prisma/language-tools/issues/1276) - [Auto completion of `directUrl`](https://togithub.com/prisma/language-tools/issues/1359) #### Credits Huge thanks to [@rintaun](https://togithub.com/rintaun), [@ivan](https://togithub.com/ivan), [@Mini256](https://togithub.com/Mini256), [@yukukotani](https://togithub.com/yukukotani), [@sandrewTx08](https://togithub.com/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**.Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.