diff --git a/apps/blog/content/blog/about-mcp-servers-and-how-we-built-one-for-prisma/index.mdx b/apps/blog/content/blog/about-mcp-servers-and-how-we-built-one-for-prisma/index.mdx index 0c63570311..9de9b9dc76 100644 --- a/apps/blog/content/blog/about-mcp-servers-and-how-we-built-one-for-prisma/index.mdx +++ b/apps/blog/content/blog/about-mcp-servers-and-how-we-built-one-for-prisma/index.mdx @@ -176,7 +176,7 @@ In the case of Prisma, the LLM primarily needs access to the Prisma CLI in order ### Enabling LLMs to call Prisma CLI commands -The Prisma MCP server is quite simple and lightweight—[you can explore it on GitHub](https://github.com/prisma/prisma/blob/main/packages/cli/src/mcp/MCP.ts). It has been packaged as part of the Prisma CLI and can be started with the following command: +The Prisma MCP server is quite simple and lightweight—[you can explore it on GitHub](https://github.com/prisma/orm/blob/main/packages/cli/src/mcp/MCP.ts). It has been packaged as part of the Prisma CLI and can be started with the following command: ```shell prisma mcp diff --git a/apps/blog/content/blog/agents-md-for-databases/index.mdx b/apps/blog/content/blog/agents-md-for-databases/index.mdx index d5591bb40f..7e2b0534ae 100644 --- a/apps/blog/content/blog/agents-md-for-databases/index.mdx +++ b/apps/blog/content/blog/agents-md-for-databases/index.mdx @@ -135,4 +135,4 @@ They solve different problems. AGENTS.md is instructions: how the agent should b Copy the block, commit it, and the next time your agent touches the database it knows where scratch databases come from, how to rehearse a migration, and when to stop and ask. Five short rules, and "wait, which database did you just reset?" becomes a question you should rarely have to ask again. -To stay up-to-date about everything that's happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/prisma) or reach out to us on [Discord](https://pris.ly/discord). +To stay up-to-date about everything that's happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/orm) or reach out to us on [Discord](https://pris.ly/discord). diff --git a/apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx b/apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx index 7f5b07b157..155989bf11 100644 --- a/apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx +++ b/apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx @@ -20,7 +20,7 @@ We are thrilled to announce the [Prisma Ambassador Program](https://www.prisma.i We're continuosly amazed by the awesome content produced by the [Prisma community](https://www.prisma.io/community), be it in the form of example projects, video tutorials or blog articles! -Not to mention how community members support each other in [GitHub Discussions](https://github.com/prisma/prisma/discussions) and on [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) or have lively discussions and show off their Prisma projects on [Slack](https://slack.prisma.io) (join the [`#showcase`](https://app.slack.com/client/T0MQBS8JG/C565176N6) channel to learn more). +Not to mention how community members support each other in [GitHub Discussions](https://github.com/prisma/orm/discussions) and on [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) or have lively discussions and show off their Prisma projects on [Slack](https://slack.prisma.io) (join the [`#showcase`](https://app.slack.com/client/T0MQBS8JG/C565176N6) channel to learn more). {/* */} @@ -38,8 +38,8 @@ While Prisma has become significantly more popular over the past year, we're dee To make adoption easier and help our users be more successful with Prisma, we ... -- ... provide dedicated community support via [GitHub Discussions](https://github.com/prisma/prisma/discussions) and [Slack](https://slack.prisma.io) -- ... incorporate feedback in our roadmap and release new versions [every two weeks](https://github.com/prisma/prisma) +- ... provide dedicated community support via [GitHub Discussions](https://github.com/prisma/orm/discussions) and [Slack](https://slack.prisma.io) +- ... incorporate feedback in our roadmap and release new versions [every two weeks](https://github.com/prisma/orm) - ... invest heavily in education e.g. via extensive [documentation](https://www.prisma.io/docs) and [videos](https://pris.ly/youtube) However, ultimately, **peer to peer feedback is indeed the most influencial approach there is**, and we want to reward those contributors who help spread the word about Prisma. @@ -80,7 +80,7 @@ We prize quality over quantity. If you're already building valuable Prisma conte If you want to become an Ambassador, your mission is to: - Produce at least 1 piece of content per quarter -- Answer at least 1 question on [GitHub Discussions](https://github.com/prisma/prisma/discussions) or [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) per quarter +- Answer at least 1 question on [GitHub Discussions](https://github.com/prisma/orm/discussions) or [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) per quarter - Attend our quarterly Ambassador Board meetings The more you contribute the more we'll reward you! You can find more information about the program on the new [Ambassador Program website](https://www.prisma.io/ambassador) and the [FAQs](https://pris.ly/ambassador-faq). diff --git a/apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx b/apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx index d478344b68..fd20bb58db 100644 --- a/apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx +++ b/apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx @@ -37,7 +37,7 @@ The jungle of existing tools and lack of best practices have two main consequenc Prisma is an open source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated and type-safe query builder for Node.js and TypeScript. -Prisma currently supports **PostgreSQL**, **MySQL** and **SQLite** databases – with more planned. Please create [new GitHub issues](https://github.com/prisma/prisma/issues/new) or subscribe to existing ones (e.g. for [MongoDB](https://github.com/prisma/prisma/issues?q=is%3Aissue+is%3Aopen+mongo) or [DynamoDB](https://github.com/prisma/prisma/issues/1676)) if you'd like to see support for specific databases. +Prisma currently supports **PostgreSQL**, **MySQL** and **SQLite** databases – with more planned. Please create [new GitHub issues](https://github.com/prisma/orm/issues/new) or subscribe to existing ones (e.g. for [MongoDB](https://github.com/prisma/orm/issues?q=is%3Aissue+is%3Aopen+mongo) or [DynamoDB](https://github.com/prisma/orm/issues/1676)) if you'd like to see support for specific databases. After running the Preview and Beta versions of Prisma 2.0 for almost a year and gathering lots of helpful feedback from our community, we are excited to launch Prisma Client for General Availability 🎉 diff --git a/apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx b/apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx index fb309216b6..a777fdbfb1 100644 --- a/apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx +++ b/apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx @@ -11,7 +11,7 @@ heroImagePath: "/announcing-prisma-2-zq1s745db8i5/imgs/hero-34a26858c7de3cad0d84 heroImageAlt: "Prisma 2 Preview: Type-safe Database Access & Declarative Migrations" --- -We are excited to share the Prisma 2 Preview today. It features a **type-safe database client** ([Photon](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020)) and a **declarative migration system** ([Lift](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020)). Help us improve Prisma 2 by trying it out and sharing your feedback! +We are excited to share the Prisma 2 Preview today. It features a **type-safe database client** ([Photon](https://github.com/prisma/orm/releases/tag/2.0.0-preview020)) and a **declarative migration system** ([Lift](https://github.com/prisma/orm/releases/tag/2.0.0-preview020)). Help us improve Prisma 2 by trying it out and sharing your feedback! This is an early Preview of Prisma 2. Current [limitations](https://github.com/prisma/prisma2/blob/master/docs/limitations.md) include missing features, limited performance and stability issues. We will address all these limitations before issuing a stable release later this year. @@ -19,8 +19,8 @@ This is an early Preview of Prisma 2. Current [limitations](https://github.com/p Today we're launching a first Preview of Prisma 2. It consists of two major tools that simplify and modernize database workflows: -- [Photon](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020): A type-safe and auto-generated databases client (_think: ORM_) -- [Lift](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020): Declarative data modeling and database migrations +- [Photon](https://github.com/prisma/orm/releases/tag/2.0.0-preview020): A type-safe and auto-generated databases client (_think: ORM_) +- [Lift](https://github.com/prisma/orm/releases/tag/2.0.0-preview020): Declarative data modeling and database migrations Photon and Lift can be used _standalone_ or _together_ in your application. Prisma 2 will be running in Preview for a few months. Please try it out and share your feedback! @@ -60,8 +60,8 @@ After helping large companies and individual developers solving their data acces Prisma 2 encompasses two standalone tools to tackle the problems of data access and migrations: -- [**Photon**](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020): A type-safe database client for more efficient and safe database access -- [**Lift**](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020): A modern and declarative migration system with custom workflows +- [**Photon**](https://github.com/prisma/orm/releases/tag/2.0.0-preview020): A type-safe database client for more efficient and safe database access +- [**Lift**](https://github.com/prisma/orm/releases/tag/2.0.0-preview020): A modern and declarative migration system with custom workflows Let's take a look at Photon and Lift in more detail. @@ -71,7 +71,7 @@ Let's take a look at Photon and Lift in more detail. Photon is a type-safe database client that's auto-generated based on the Prisma data model (which is a representation of your database schema). It provides a powerful and lightweight layer of mapping code you can use to talk to a database in your application. -It has a modern and ergonomic data access API that's tailored to the needs of application developers. You can explore the Photon API on the [Photon site](https://github.com/prisma/prisma/releases/tag/2.0.0-preview020). +It has a modern and ergonomic data access API that's tailored to the needs of application developers. You can explore the Photon API on the [Photon site](https://github.com/prisma/orm/releases/tag/2.0.0-preview020). ### Lift – Declarative data modeling & migrations diff --git a/apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx b/apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx index b3dfc5194e..fd1420ff80 100644 --- a/apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx +++ b/apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx @@ -14,7 +14,7 @@ tags: - "orm" --- -We just released Prisma [6.18.0](https://github.com/prisma/prisma/releases/tag/6.18.0) with several bug fixes and improvments. Additionally, we added more support for the Prisma Config file to prepare for the next major release of Prisma ORM. +We just released Prisma [6.18.0](https://github.com/prisma/orm/releases/tag/6.18.0) with several bug fixes and improvments. Additionally, we added more support for the Prisma Config file to prepare for the next major release of Prisma ORM. ## In-depth Database Metrics diff --git a/apps/blog/content/blog/announcing-prisma-orm-7-0-0/index.mdx b/apps/blog/content/blog/announcing-prisma-orm-7-0-0/index.mdx index d639d43d28..3768eba58a 100644 --- a/apps/blog/content/blog/announcing-prisma-orm-7-0-0/index.mdx +++ b/apps/blog/content/blog/announcing-prisma-orm-7-0-0/index.mdx @@ -102,7 +102,7 @@ All of this is possible because Prisma Postgres is just standard Postgres, but b ## What else is changing -There’s a lot in this release that we would love to talk about, but then this post would be much longer. We're already grateful you read this far! We’ve spent countless hours working through our backlog of issues and feature requests to address some of the top requested ones, like [mapped enums](https://github.com/prisma/prisma/issues/273?utm_source=blog&utm_content=launch-blog&via=prisma7), updating the minimum version of Node and TypeScript required for projects, as well as a brand new version of Prisma Studio via `npx prisma studio`. You can find **everything** that’s in this release in our changelog, and we have a migrations guide available as well. +There’s a lot in this release that we would love to talk about, but then this post would be much longer. We're already grateful you read this far! We’ve spent countless hours working through our backlog of issues and feature requests to address some of the top requested ones, like [mapped enums](https://github.com/prisma/orm/issues/273?utm_source=blog&utm_content=launch-blog&via=prisma7), updating the minimum version of Node and TypeScript required for projects, as well as a brand new version of Prisma Studio via `npx prisma studio`. You can find **everything** that’s in this release in our changelog, and we have a migrations guide available as well. ## Where to go next @@ -120,4 +120,4 @@ For migration guides and additional resources, please check out the links below. - [Prisma ORM Changelog](https://www.prisma.io/changelog?utm_source=blog&utm_content=launch-blog&via=prisma7) - [Prisma Postgres](https://www.prisma.io/postgres?utm_source=blog&utm_content=launch-blog&via=prisma7) - [Prisma ORM](http://prisma.io/orm?utm_source=blog&utm_content=launch-blog&via=prisma7) -- [Prisma ORM repo on GitHub](https://github.com/prisma/prisma?utm_source=blog&utm_content=launch-blog&via=prisma7) +- [Prisma ORM repo on GitHub](https://github.com/prisma/orm?utm_source=blog&utm_content=launch-blog&via=prisma7) diff --git a/apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx b/apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx index f95456fcf9..821cea317d 100644 --- a/apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx +++ b/apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx @@ -16,7 +16,7 @@ With AI-native IDEs, we are all developing apps with remarkable speed. So much s The [Model-Context-Protocol](https://modelcontextprotocol.io/introduction) (MCP) gives LLMs a way to call APIs and thus access external systems in a well-defined manner. Prisma's MCP server gives LLMs the ability to manage [Prisma Postgres](https://www.prisma.io/postgres) databases (e.g. spin up new database instances or run schema migrations). -We're excited to share that as of [v6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0), the Prisma CLI now comes with a built-in MCP server that you can integrate in your favorite AI tool using this snippet: +We're excited to share that as of [v6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0), the Prisma CLI now comes with a built-in MCP server that you can integrate in your favorite AI tool using this snippet: ```js { diff --git a/apps/blog/content/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm/index.mdx b/apps/blog/content/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm/index.mdx index ce1272f283..13a5500393 100644 --- a/apps/blog/content/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm/index.mdx +++ b/apps/blog/content/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm/index.mdx @@ -16,7 +16,7 @@ tags: [TypedSQL](https://www.prisma.io/docs/orm/v7/prisma-client/using-raw-sql/typedsql) is a Prisma ORM feature that turns raw SQL queries written in `.sql` files into fully typed TypeScript functions. You write plain SQL, run `prisma generate --sql`, and Prisma ORM generates a function with typed arguments and a typed result that you execute with `$queryRawTyped`. This guide walks through the complete workflow on Prisma ORM 7. -> **Updated (July 2026):** This post originally announced TypedSQL in Prisma ORM [v5.19.0](https://github.com/prisma/prisma/releases/tag/5.19.0). It is now maintained as an evergreen guide. TypedSQL remains a Preview feature in Prisma ORM 7. Every command and code block below was run end-to-end against `prisma@7.8` and `@prisma/client@7.8`, using the `prisma-client` generator and a local [Prisma Postgres](https://www.prisma.io/docs/postgres) database started with `npx prisma dev`. +> **Updated (July 2026):** This post originally announced TypedSQL in Prisma ORM [v5.19.0](https://github.com/prisma/orm/releases/tag/5.19.0). It is now maintained as an evergreen guide. TypedSQL remains a Preview feature in Prisma ORM 7. Every command and code block below was run end-to-end against `prisma@7.8` and `@prisma/client@7.8`, using the `prisma-client` generator and a local [Prisma Postgres](https://www.prisma.io/docs/postgres) database started with `npx prisma dev`. ## How TypedSQL works diff --git a/apps/blog/content/blog/bringing-prisma-orm-to-react-native-and-expo/index.mdx b/apps/blog/content/blog/bringing-prisma-orm-to-react-native-and-expo/index.mdx index 5af1d181d6..f3ab375a1f 100644 --- a/apps/blog/content/blog/bringing-prisma-orm-to-react-native-and-expo/index.mdx +++ b/apps/blog/content/blog/bringing-prisma-orm-to-react-native-and-expo/index.mdx @@ -18,7 +18,7 @@ Prisma ORM is the preferred way to work with databases in backend JavaScript app -We got the first request to support React Native back in 2019, and since then [the issue has gotten more than 300 upvotes](https://github.com/prisma/prisma/issues/5011). We always wanted Prisma to power the data of local apps - both on mobile, web and desktop, so this community interest made sense to us. But we also knew that porting Prisma ORM to mobile wouldn’t cut it. Apps are different than web servers, and to provide excellent DX, we would need to build additional functionality to offer tight integration with the underlying platform. So that’s what we have been doing, and today, we are excited to announce the [Early Access of Prisma ORM for React Native and Expo](https://github.com/prisma/react-native-prisma) 🎉  +We got the first request to support React Native back in 2019, and since then [the issue has gotten more than 300 upvotes](https://github.com/prisma/orm/issues/5011). We always wanted Prisma to power the data of local apps - both on mobile, web and desktop, so this community interest made sense to us. But we also knew that porting Prisma ORM to mobile wouldn’t cut it. Apps are different than web servers, and to provide excellent DX, we would need to build additional functionality to offer tight integration with the underlying platform. So that’s what we have been doing, and today, we are excited to announce the [Early Access of Prisma ORM for React Native and Expo](https://github.com/prisma/react-native-prisma) 🎉  We have worked with [Expo](https://expo.dev/) to make sure it’s easy to use in an app managed by Expo, and the readme contains documentation to set up Prisma ORM in a React Native app not managed by Expo. diff --git a/apps/blog/content/blog/build-applications-at-the-edge-with-prisma-orm-and-cloudflare-d1-preview/index.mdx b/apps/blog/content/blog/build-applications-at-the-edge-with-prisma-orm-and-cloudflare-d1-preview/index.mdx index c81a207718..974f790cc1 100644 --- a/apps/blog/content/blog/build-applications-at-the-edge-with-prisma-orm-and-cloudflare-d1-preview/index.mdx +++ b/apps/blog/content/blog/build-applications-at-the-edge-with-prisma-orm-and-cloudflare-d1-preview/index.mdx @@ -48,7 +48,7 @@ At Prisma, we believe that Cloudflare is at the forefront of building the future > You can learn more about how we think about Cloudflare as a partner in improving [Data DX](https://www.datadx.io/) in this blog post: [Developer Experience Redefined: Prisma & Cloudflare Lead the Way to Data DX](https://www.prisma.io/blog/cloudflare-partnership-qerefgvwirjq) > -[Supporting D1](https://github.com/prisma/prisma/issues/13310) has been one of the most popular feature requests for Prisma ORM on GitHub. +[Supporting D1](https://github.com/prisma/orm/issues/13310) has been one of the most popular feature requests for Prisma ORM on GitHub. ![](/build-applications-at-the-edge-with-prisma-orm-and-cloudflare-d1-preview/imgs/dece55108fc5c399e5466b8dc5d73e8e9509cab0-1480x1696.png) @@ -308,4 +308,4 @@ Congratulations, you just deployed a Cloudflare Worker using D1 as a database an ## Try it out today -We would love to hear what you think of the new D1 support in Prisma ORM! Please try it out and share your feedback with us on [GitHub](https://www.github.com/prisma/prisma/tbd) or on [Discord](https://pris.ly/discord). Happy coding ✌️ +We would love to hear what you think of the new D1 support in Prisma ORM! Please try it out and share your feedback with us on [GitHub](https://www.github.com/prisma/orm/tbd) or on [Discord](https://pris.ly/discord). Happy coding ✌️ diff --git a/apps/blog/content/blog/client-extensions-ga-4g4yIu8eOSbB/index.mdx b/apps/blog/content/blog/client-extensions-ga-4g4yIu8eOSbB/index.mdx index f1ed019ea9..e7497fe737 100644 --- a/apps/blog/content/blog/client-extensions-ga-4g4yIu8eOSbB/index.mdx +++ b/apps/blog/content/blog/client-extensions-ga-4g4yIu8eOSbB/index.mdx @@ -14,11 +14,11 @@ tags: - "announcement" --- -With the release of version [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) of the Prisma ORM, [Client extensions](https://www.prisma.io/docs/orm/v7/prisma-client/client-extensions) are now Generally Available! This new feature allows users to extend and customize Prisma Client to meet their individual use cases. +With the release of version [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) of the Prisma ORM, [Client extensions](https://www.prisma.io/docs/orm/v7/prisma-client/client-extensions) are now Generally Available! This new feature allows users to extend and customize Prisma Client to meet their individual use cases. ## Tailor Prisma Client to meet your codebase's needs -In [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0), we released Prisma Client extensions [as a Preview feature](https://www.prisma.io/docs/orm/v7/more/releases#preview). Today we are happy to announce the General Availability of Prisma Client extensions! Extensions have proven to be extremely useful and powerful during the Preview period, even powering Prisma products like [Accelerate](https://www.prisma.io/data-platform/accelerate) and [Optimize](https://www.prisma.io/docs/optimize)! +In [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0), we released Prisma Client extensions [as a Preview feature](https://www.prisma.io/docs/orm/v7/more/releases#preview). Today we are happy to announce the General Availability of Prisma Client extensions! Extensions have proven to be extremely useful and powerful during the Preview period, even powering Prisma products like [Accelerate](https://www.prisma.io/data-platform/accelerate) and [Optimize](https://www.prisma.io/docs/optimize)! ### A straightforward and easy to use API @@ -65,7 +65,7 @@ const prisma = new PrismaClient().$extends({ const postExists = await prisma.post.exists({ id: 1 }); ``` -For a more in-depth look into changes we made to the extensions API as a part of this release, please check out [our release notes](https://github.com/prisma/prisma/releases/tag/4.16.0) +For a more in-depth look into changes we made to the extensions API as a part of this release, please check out [our release notes](https://github.com/prisma/orm/releases/tag/4.16.0) ### Extensions built by the community diff --git a/apps/blog/content/blog/cockroach-ga-5JrD9XVWQDYL/index.mdx b/apps/blog/content/blog/cockroach-ga-5JrD9XVWQDYL/index.mdx index 3bf2bbff17..4fdc68e20d 100644 --- a/apps/blog/content/blog/cockroach-ga-5JrD9XVWQDYL/index.mdx +++ b/apps/blog/content/blog/cockroach-ga-5JrD9XVWQDYL/index.mdx @@ -14,13 +14,13 @@ tags: - "orm" --- -On May 10th, we were thrilled to release version [3.14.0](https://github.com/prisma/prisma/releases/tag/3.14.0) of +On May 10th, we were thrilled to release version [3.14.0](https://github.com/prisma/orm/releases/tag/3.14.0) of Prisma ORM, which brought [CockroachDB](https://www.cockroachlabs.com/product/) support to GA! This production-ready feature allows developers to make use of a scalable and resilient database. ## CockroachDB support in Prisma is now Generally Available 💙 -Back in February, as part of the [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) release of Prisma, preview support for CockroachDB was added. Today, as CockroachDB announces their 22.1 release, we are excited to officially announce the general availability of Prisma's CockroachDB connector. +Back in February, as part of the [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) release of Prisma, preview support for CockroachDB was added. Today, as CockroachDB announces their 22.1 release, we are excited to officially announce the general availability of Prisma's CockroachDB connector. Thanks to the amazing community feedback and testing, along with collaboration from the amazing [Cockroach Labs](https://www.cockroachlabs.com/) team, this feature is now production-ready! diff --git a/apps/blog/content/blog/data-migrations-in-prisma-next/index.mdx b/apps/blog/content/blog/data-migrations-in-prisma-next/index.mdx index db67b59b9f..cd031059c8 100644 --- a/apps/blog/content/blog/data-migrations-in-prisma-next/index.mdx +++ b/apps/blog/content/blog/data-migrations-in-prisma-next/index.mdx @@ -74,7 +74,7 @@ There's also a quieter problem. The script uses your _current_ Prisma client, wh Whichever path you pick, your data transformation doesn't have access to the same tools, verifications or editor assistance as the rest of your application logic. -People have asked for the obvious fix, being able to use the Prisma client _inside_ a migration, for years (the [docs](https://www.prisma.io/docs/orm/v7/prisma-migrate/workflows/customizing-migrations) point at the SQL or out-of-band script as the official answers; and there are many open issues with suggestions for how to integrate the TypeScript client and migrations: [#11194](https://github.com/prisma/prisma/issues/11194), [#4688](https://github.com/prisma/prisma/issues/4688), [#6345](https://github.com/prisma/prisma/issues/6345), [#10050](https://github.com/prisma/prisma/issues/10050)). +People have asked for the obvious fix, being able to use the Prisma client _inside_ a migration, for years (the [docs](https://www.prisma.io/docs/orm/v7/prisma-migrate/workflows/customizing-migrations) point at the SQL or out-of-band script as the official answers; and there are many open issues with suggestions for how to integrate the TypeScript client and migrations: [#11194](https://github.com/prisma/orm/issues/11194), [#4688](https://github.com/prisma/orm/issues/4688), [#6345](https://github.com/prisma/orm/issues/6345), [#10050](https://github.com/prisma/orm/issues/10050)). ## In Prisma 8, you write the data step in TypeScript @@ -204,7 +204,7 @@ dataTransform(endContract, "backfill-product-status", { }); ``` -Same `check` and `run` callbacks. Same compilation to a JSON file. Same kind of typed query against a contract snapshot specific to this migration. The query language is Mongo's, `.match(...).updateMany(...)` instead of `.where(...).update(...)`, but everything else carries over. There's a fully working example [in the Prisma repo](https://github.com/prisma/prisma/blob/main/examples/retail-store/migrations/app/20260513T0508_backfill_product_status/migration.ts), and we'll cover Mongo data migrations in more depth in a follow-up post. +Same `check` and `run` callbacks. Same compilation to a JSON file. Same kind of typed query against a contract snapshot specific to this migration. The query language is Mongo's, `.match(...).updateMany(...)` instead of `.where(...).update(...)`, but everything else carries over. There's a fully working example [in the Prisma repo](https://github.com/prisma/orm/blob/main/examples/retail-store/migrations/app/20260513T0508_backfill_product_status/migration.ts), and we'll cover Mongo data migrations in more depth in a follow-up post. ## Try it yourself @@ -216,6 +216,6 @@ npx prisma@latest orm init This command will set up Prisma 8 in a new or existing project with a simple example contract. Write a schema change with a data step in the same file, plan it, read the JSON it compiled to, and apply it. -Tell us what worked and what didn't on [Discord](https://pris.ly/discord) in the `#prisma-next` channel, and **star and watch [prisma/prisma](https://github.com/prisma/prisma) on GitHub** to follow development. We'd love to hear your feedback! +Tell us what worked and what didn't on [Discord](https://pris.ly/discord) in the `#prisma-next` channel, and **star and watch [prisma/prisma](https://github.com/prisma/orm) on GitHub** to follow development. We'd love to hear your feedback! Prisma 8 is a Release Candidate. Prisma 7 is the current generally available release, so if you're using it, keep using it. diff --git a/apps/blog/content/blog/database-access-in-react-server-components-r2xgk9aztgdf/index.mdx b/apps/blog/content/blog/database-access-in-react-server-components-r2xgk9aztgdf/index.mdx index dacd7d1050..dce2c3e236 100644 --- a/apps/blog/content/blog/database-access-in-react-server-components-r2xgk9aztgdf/index.mdx +++ b/apps/blog/content/blog/database-access-in-react-server-components-r2xgk9aztgdf/index.mdx @@ -29,7 +29,7 @@ Here's the [RFC](https://github.com/reactjs/rfcs/pull/188) and the full announc -This article summarizes the talk while making some changes to the official demo. Instead of sending raw SQL queries to the database, we'll be using **Prisma**, an [open-source](https://github.com/prisma/prisma) ORM. +This article summarizes the talk while making some changes to the official demo. Instead of sending raw SQL queries to the database, we'll be using **Prisma**, an [open-source](https://github.com/prisma/orm) ORM. If you have watched the talk already, feel free to skip to the [demo](#server-components-demo) section of this article. Using Prisma instead of plain SQL has several benefits: diff --git a/apps/blog/content/blog/database-vs-application-demystifying-join-strategies/index.mdx b/apps/blog/content/blog/database-vs-application-demystifying-join-strategies/index.mdx index e19ac48052..6ef10f483c 100644 --- a/apps/blog/content/blog/database-vs-application-demystifying-join-strategies/index.mdx +++ b/apps/blog/content/blog/database-vs-application-demystifying-join-strategies/index.mdx @@ -326,7 +326,7 @@ While the approach of application-level joins has served most developers well, i That's why [we've added the smart DB-level joins as an alternative one year ago](https://www.prisma.io/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview), so developers have the option to always choose the most performant join strategy for their individual use case. -Being able to use DB-level joins had been one of the [most popular feature requests](https://github.com/prisma/prisma/issues/5184) of Prisma ORM and has been received well by our community since it was released in Preview. Once this feature becomes generally available, DB-level joins will become the default join strategy Prisma ORM applies for its relation queries. +Being able to use DB-level joins had been one of the [most popular feature requests](https://github.com/prisma/orm/issues/5184) of Prisma ORM and has been received well by our community since it was released in Preview. Once this feature becomes generally available, DB-level joins will become the default join strategy Prisma ORM applies for its relation queries. [Community feedback is one of the major drivers that helps us prioritize](https://www.prisma.io/blog/prisma-orm-manifesto#2-clearer-issue-management-community-prioritization-and-engagement) what we're working on to improve Prisma ORM. diff --git a/apps/blog/content/blog/datamodel-v11-lrzqy1f56c90/index.mdx b/apps/blog/content/blog/datamodel-v11-lrzqy1f56c90/index.mdx index 4fdacd5128..3eef343e20 100644 --- a/apps/blog/content/blog/datamodel-v11-lrzqy1f56c90/index.mdx +++ b/apps/blog/content/blog/datamodel-v11-lrzqy1f56c90/index.mdx @@ -15,7 +15,7 @@ Prisma's latest release features an improved datamodel syntax. It removes many o > ⚠️ **This article is outdated** as it relates to [Prisma 1](https://github.com/prisma/prisma1) which is now [deprecated](https://github.com/prisma/prisma1/issues/5208). To learn more about the most recent version of Prisma, read the [documentation](https://www.prisma.io/docs). ⚠️ -Over the last months, we have worked with the community to define an improved datamodel [specification](https://github.com/prisma/prisma/issues/3408) for Prisma. This new version is called datamodel v1.1 and is available in today's stable release. Check out the docs [here](https://v1.prisma.io/docs/1.31/releases-and-maintenance/features-in-preview/datamodel-v11-b6a7/). +Over the last months, we have worked with the community to define an improved datamodel [specification](https://github.com/prisma/orm/issues/3408) for Prisma. This new version is called datamodel v1.1 and is available in today's stable release. Check out the docs [here](https://v1.prisma.io/docs/1.31/releases-and-maintenance/features-in-preview/datamodel-v11-b6a7/). > As of today, Prisma's public [Demo servers](https://v1.prisma.io/docs/1.31/prisma-server/demo-servers-prisma-cloud-jfr3) will be using the new datamodel syntax. Check out the [**docs**](https://v1.prisma.io/docs/1.31/releases-and-maintenance/features-in-preview/datamodel-v11-b6a7/#upgrading-to-datamodel-v11) or this [**tutorial video**](https://www.youtube.com/watch?v=48m1Gnmu19Q) to learn how to upgrade your existing projects. @@ -584,7 +584,7 @@ To access your data in [Prisma Admin](https://v1.prisma.io/docs/1.31/prisma-admi ## Share you feedback and ideas -While the new datamodel syntax already incorporates many features requested by our community, we still see opportunities to improve it even further. For example, the datamodel doesn't yet provide [multi-column indices](https://github.com/prisma/prisma/issues/3405) and [polymorphic relations](https://github.com/prisma/prisma/issues/3407). +While the new datamodel syntax already incorporates many features requested by our community, we still see opportunities to improve it even further. For example, the datamodel doesn't yet provide [multi-column indices](https://github.com/prisma/orm/issues/3405) and [polymorphic relations](https://github.com/prisma/orm/issues/3407). We are currently working on a new [data modeling language](https://github.com/prisma/specs/tree/master/schema) that will be a variation of the currently used [SDL](https://www.prisma.io/blog/graphql-sdl-schema-definition-language-6755bcb9ce51). diff --git a/apps/blog/content/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm/index.mdx b/apps/blog/content/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm/index.mdx index 2eb91b3aee..842858a286 100644 --- a/apps/blog/content/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm/index.mdx +++ b/apps/blog/content/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm/index.mdx @@ -17,7 +17,7 @@ The Prisma query engine, written in Rust, has always been a core part of Prisma ## TL;DR: The Rust-Free ORM is ready for production-use -Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/prisma/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. +Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/orm/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. - **No binary overhead:** The dependency on native Rust binaries is eliminated, drastically simplifying deployment and reducing potential complexity issues. - **Performance:** Get **up to 3.4x faster queries** (by removing cross-language serialization) and a **90% smaller bundle size** (from ~14MB to 1.6 MB). @@ -124,8 +124,8 @@ This project is a significant step toward making Prisma ORM better for everyone. Here’s how you can help: -- [File issues](https://github.com/prisma/prisma/issues/new/choose) to report bugs or suggest features. -- [Use discussions](https://github.com/prisma/prisma/discussions) to share your ideas. +- [File issues](https://github.com/prisma/orm/issues/new/choose) to report bugs or suggest features. +- [Use discussions](https://github.com/prisma/orm/discussions) to share your ideas. - [Join our Discord](https://pris.ly/discord) to participate in community events and dev AMAs. Finally, test our Early Access client! We’ll share updates on GitHub and Discord. diff --git a/apps/blog/content/blog/give-your-agent-a-database/index.mdx b/apps/blog/content/blog/give-your-agent-a-database/index.mdx index 2518976d7e..50e8c77951 100644 --- a/apps/blog/content/blog/give-your-agent-a-database/index.mdx +++ b/apps/blog/content/blog/give-your-agent-a-database/index.mdx @@ -174,4 +174,4 @@ npx create-db@latest --json Run it, hand the connection string to your agent, and let it test against real Postgres. If the result is worth keeping, claim the database and keep building on it. The [create-db documentation](https://www.prisma.io/docs/postgres/npx-create-db) covers the CLI options, the web interface, and the claim flow in detail. -To stay up-to-date about everything that's happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/prisma) or reach out to us on [Discord](https://pris.ly/discord). +To stay up-to-date about everything that's happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/orm) or reach out to us on [Discord](https://pris.ly/discord). diff --git a/apps/blog/content/blog/how-prisma-orm-became-the-most-downloaded-orm-for-node-js/index.mdx b/apps/blog/content/blog/how-prisma-orm-became-the-most-downloaded-orm-for-node-js/index.mdx index 55ba5725dd..d17df629e8 100644 --- a/apps/blog/content/blog/how-prisma-orm-became-the-most-downloaded-orm-for-node-js/index.mdx +++ b/apps/blog/content/blog/how-prisma-orm-became-the-most-downloaded-orm-for-node-js/index.mdx @@ -134,4 +134,4 @@ A large share of registry-wide growth comes from AI coding agents. Agents instal -To stay up-to-date about everything that’s happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/prisma) or reach out to us on [Discord](https://pris.ly/discord). +To stay up-to-date about everything that’s happening in the Prismaverse, keep an eye on our [changelog](https://www.prisma.io/changelog) and [follow us on X](https://pris.ly/x)! And if you have ideas for how Prisma can be improved, always feel free to open an issue on [GitHub](https://github.com/prisma/orm) or reach out to us on [Discord](https://pris.ly/discord). diff --git a/apps/blog/content/blog/how-prisma-supports-transactions-x45s1d5l0ww1/index.mdx b/apps/blog/content/blog/how-prisma-supports-transactions-x45s1d5l0ww1/index.mdx index 912a7d88ae..b99271766f 100644 --- a/apps/blog/content/blog/how-prisma-supports-transactions-x45s1d5l0ww1/index.mdx +++ b/apps/blog/content/blog/how-prisma-supports-transactions-x45s1d5l0ww1/index.mdx @@ -89,7 +89,7 @@ Later in this article, we will explore situations an alternative approach can pr Prisma is built with the support of modern deployment environments in mind. We chose an architecture separating the core [engines](https://www.prisma.io/docs/concepts/components/prisma-engines#prisma-engines) from the JavaScript/TypeScript client, enabling us to consider more complex deployment configurations in the future. -This is why [Prisma currently doesn't support the "traditional" database transaction mechanism](https://github.com/prisma/prisma/issues/1844), where an arbitrary set of queries is grouped in a transaction and either succeeds or fails as a whole. Instead, we are trying to identify various _patterns_ and _use cases_ for database transactions which we can solve in a better, more efficient manner than through long-running database transactions. +This is why [Prisma currently doesn't support the "traditional" database transaction mechanism](https://github.com/prisma/orm/issues/1844), where an arbitrary set of queries is grouped in a transaction and either succeeds or fails as a whole. Instead, we are trying to identify various _patterns_ and _use cases_ for database transactions which we can solve in a better, more efficient manner than through long-running database transactions. The following _nested writes_ and _transaction API_ are examples for certain use cases where developers would traditionally resort to long-running database transactions but where Prisma offers a more targeted and tailored API to accomplish a certain goal. @@ -150,7 +150,7 @@ We believe that there are better ways than long-running transactions to solve a Sometimes a multi-step interaction with the database can be expressed more efficiently as an _atomic operation_. -For example, if you want to read a value, increment by one and then write it back, it would be better to instead use the atomic operator `increment` to perform both steps in a single transactional query. Atomic number operators are available as a preview feature since the [v2.6.0](https://github.com/prisma/prisma/releases/tag/2.6.0) release. +For example, if you want to read a value, increment by one and then write it back, it would be better to instead use the atomic operator `increment` to perform both steps in a single transactional query. Atomic number operators are available as a preview feature since the [v2.6.0](https://github.com/prisma/orm/releases/tag/2.6.0) release. ### Application-level optimistic concurrency control (OCC) @@ -172,7 +172,7 @@ An often overlooked but sometimes very effective strategy is to intentionally re ## Share your thoughts, feedback and use cases -While we believe that the vast majority of use cases for database transactions can be resolved with better, safer and more efficient alternatives, we'd love to hear your feedback on this approach! Also, if you feel like you have use cases in your application that are not covered by any of the suggested alternatives, please make sure to [open a GitHub issue](https://github.com/prisma/prisma/issues/new/choose) so that we can address this use case as well. +While we believe that the vast majority of use cases for database transactions can be resolved with better, safer and more efficient alternatives, we'd love to hear your feedback on this approach! Also, if you feel like you have use cases in your application that are not covered by any of the suggested alternatives, please make sure to [open a GitHub issue](https://github.com/prisma/orm/issues/new/choose) so that we can address this use case as well. > **Update (July 1st, 2022)**: Since this article has been published, we have released [interactive transactions](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions-in-preview) which enables developers to use flexible, long-running transactions in Prisma Client. diff --git a/apps/blog/content/blog/introducing-global-omit-for-model-fields-in-prisma-orm-5-16-0/index.mdx b/apps/blog/content/blog/introducing-global-omit-for-model-fields-in-prisma-orm-5-16-0/index.mdx index 16320aa3e6..8f9e486914 100644 --- a/apps/blog/content/blog/introducing-global-omit-for-model-fields-in-prisma-orm-5-16-0/index.mdx +++ b/apps/blog/content/blog/introducing-global-omit-for-model-fields-in-prisma-orm-5-16-0/index.mdx @@ -78,4 +78,4 @@ If, however, you are concerned about data optimization, you will want to use a * ### We want your continued feedback! -The ability to omit fields globally is [our most requested feature](https://github.com/prisma/prisma/issues/5042) and we’re excited to include this in our 5.16.0 release. If you have feedback please do not hesitate to add to our [dedicated GitHub discussion](https://github.com/prisma/prisma/discussions/23924). We’ve had some great conversations about our `omitApi` Preview feature so far and we’re excited to keep those conversations going. +The ability to omit fields globally is [our most requested feature](https://github.com/prisma/orm/issues/5042) and we’re excited to include this in our 5.16.0 release. If you have feedback please do not hesitate to add to our [dedicated GitHub discussion](https://github.com/prisma/orm/discussions/23924). We’ve had some great conversations about our `omitApi` Preview feature so far and we’re excited to keep those conversations going. diff --git a/apps/blog/content/blog/metrics-tutorial-prisma-pmoldgq10kz/index.mdx b/apps/blog/content/blog/metrics-tutorial-prisma-pmoldgq10kz/index.mdx index 6cdf63f0a3..3800682940 100644 --- a/apps/blog/content/blog/metrics-tutorial-prisma-pmoldgq10kz/index.mdx +++ b/apps/blog/content/blog/metrics-tutorial-prisma-pmoldgq10kz/index.mdx @@ -511,7 +511,7 @@ For further reading, you can check out the following resources: - [Prometheus Documentation](https://prometheus.io/docs/introduction/overview/) - [Grafana Documentation](https://grafana.com/docs/grafana/latest/) -We would love to get your thoughts on the metrics feature! Please give us feedback about metrics on this [Github issue](https://github.com/prisma/prisma/issues/13579). +We would love to get your thoughts on the metrics feature! Please give us feedback about metrics on this [Github issue](https://github.com/prisma/orm/issues/13579). You can find the source code for this project on [GitHub](https://github.com/prisma/metrics-tutorial-prisma). Please feel free to raise an issue in the repository or submit a PR if you notice a problem. You can also reach out to me directly on [Twitter](https://twitter.com/tasinishmam). diff --git a/apps/blog/content/blog/mongodb-general-availability-pixnun6mffmu/index.mdx b/apps/blog/content/blog/mongodb-general-availability-pixnun6mffmu/index.mdx index 9ae3e0fbc6..402d3dcf09 100644 --- a/apps/blog/content/blog/mongodb-general-availability-pixnun6mffmu/index.mdx +++ b/apps/blog/content/blog/mongodb-general-availability-pixnun6mffmu/index.mdx @@ -14,11 +14,11 @@ tags: - "orm" --- -We are excited to share that today's Prisma ORM [release](https://github.com/prisma/prisma/releases/tag/3.12.0) adds stable and production-ready support for MongoDB! Join our celebrations during the [launch week](https://www.prisma.io/mongodb?utm_source=website&utm_medium=blogpost&utm_campaign=mongodblaunch) **April 25-29**. +We are excited to share that today's Prisma ORM [release](https://github.com/prisma/orm/releases/tag/3.12.0) adds stable and production-ready support for MongoDB! Join our celebrations during the [launch week](https://www.prisma.io/mongodb?utm_source=website&utm_medium=blogpost&utm_campaign=mongodblaunch) **April 25-29**. ## Prisma + MongoDB = 💚 -Support for [MongoDB](https://www.mongodb.com/) has been one of the [most requested features](https://github.com/prisma/prisma/issues/1277) since the initial release of the Prisma ORM. Using both technologies together makes developers more productive and allows them to ship more ambitious software faster. +Support for [MongoDB](https://www.mongodb.com/) has been one of the [most requested features](https://github.com/prisma/orm/issues/1277) since the initial release of the Prisma ORM. Using both technologies together makes developers more productive and allows them to ship more ambitious software faster. ![](/mongodb-general-availability-pixnun6mffmu/imgs/issue.png) diff --git a/apps/blog/content/blog/mongodb-without-compromise/index.mdx b/apps/blog/content/blog/mongodb-without-compromise/index.mdx index 3996eefd6a..63baae61ae 100644 --- a/apps/blog/content/blog/mongodb-without-compromise/index.mdx +++ b/apps/blog/content/blog/mongodb-without-compromise/index.mdx @@ -254,6 +254,6 @@ The MongoDB Node.js Driver team's input from user-journey research and feature-g We believe this raises the bar for what MongoDB developers should expect from their tools. -- **Star + watch the repo:** [github.com/prisma/prisma](https://github.com/prisma/prisma) -- **Try the Mongo demo app:** [examples/mongo-demo](https://github.com/prisma/prisma/tree/main/examples/mongo-demo) +- **Star + watch the repo:** [github.com/prisma/orm](https://github.com/prisma/orm) +- **Try the Mongo demo app:** [examples/mongo-demo](https://github.com/prisma/orm/tree/main/examples/mongo-demo) - **Join the conversation:** [Discord](http://pris.ly/discord) diff --git a/apps/blog/content/blog/organize-your-prisma-schema-with-multi-file-support/index.mdx b/apps/blog/content/blog/organize-your-prisma-schema-with-multi-file-support/index.mdx index d9e8e11b0c..8cc9bfb3b9 100644 --- a/apps/blog/content/blog/organize-your-prisma-schema-with-multi-file-support/index.mdx +++ b/apps/blog/content/blog/organize-your-prisma-schema-with-multi-file-support/index.mdx @@ -17,7 +17,7 @@ tags: Prisma ORM lets you [organize your Prisma Schema into multiple files](https://www.prisma.io/docs/orm/v7/prisma-schema/overview/location#multi-file-prisma-schema). You split your models across as many `.prisma` files as you like, relations work across files without any imports, and Prisma combines everything when you run `prisma generate` or a migration command. The feature is Generally Available since v6.7.0, so no preview flag is needed. In Prisma ORM v7, you point the `schema` property in `prisma.config.ts` at the directory that holds your schema files. This post shows the setup, when to split, and the pitfalls to avoid. -Multi-file schemas were [one of our most requested features](https://github.com/prisma/prisma/issues/2377): they first shipped as the `prismaSchemaFolder` Preview feature in v5.15 and went GA in [v6.7.0](https://github.com/prisma/prisma/releases/tag/6.7.0). +Multi-file schemas were [one of our most requested features](https://github.com/prisma/orm/issues/2377): they first shipped as the `prismaSchemaFolder` Preview feature in v5.15 and went GA in [v6.7.0](https://github.com/prisma/orm/releases/tag/6.7.0). ### How to split your Prisma Schema into multiple files diff --git a/apps/blog/content/blog/orm-6-10-0-new-features-for-prisma-postgres-remote-mcp-and-more/index.mdx b/apps/blog/content/blog/orm-6-10-0-new-features-for-prisma-postgres-remote-mcp-and-more/index.mdx index f9c46d1e97..0e55aa20f2 100644 --- a/apps/blog/content/blog/orm-6-10-0-new-features-for-prisma-postgres-remote-mcp-and-more/index.mdx +++ b/apps/blog/content/blog/orm-6-10-0-new-features-for-prisma-postgres-remote-mcp-and-more/index.mdx @@ -75,7 +75,7 @@ Here the MCP server is in action, creating a new database directly in the Warp A ## Prisma ORM v6.10.0 with major improvements -We just released [Prisma ORM v6.10.0](https://www.github.com/prisma/prisma/releases/tag/6.10.0) with some new highlights, read more below! +We just released [Prisma ORM v6.10.0](https://www.github.com/prisma/orm/releases/tag/6.10.0) with some new highlights, read more below! ### No Rust engines for MS SQL Server & PlanetScale (Preview) diff --git a/apps/blog/content/blog/orm-v6-17-0-new-usage-metrics-and-direct-connections-in-ga-for-prisma-postgres/index.mdx b/apps/blog/content/blog/orm-v6-17-0-new-usage-metrics-and-direct-connections-in-ga-for-prisma-postgres/index.mdx index 9db523d11e..ab6b00925e 100644 --- a/apps/blog/content/blog/orm-v6-17-0-new-usage-metrics-and-direct-connections-in-ga-for-prisma-postgres/index.mdx +++ b/apps/blog/content/blog/orm-v6-17-0-new-usage-metrics-and-direct-connections-in-ga-for-prisma-postgres/index.mdx @@ -68,10 +68,10 @@ Here's what's new: const adapter = new PrismaMssql(config) const prisma = new PrismaClient({ adapter }) ``` - Learn more in this [PR](https://github.com/prisma/prisma/pull/28156/files#diff-351f5d894309f058776099c378e3956271f34f34c04e2b54576045b9773ab61aR61-R62). -- Relaxed the support package range for `@opentelemetry/instrumentation` to be compatible with `">=0.52.0 <1"`. Learn more in this [PR](https://github.com/prisma/prisma/pull/28199/files). -- Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this [PR](https://github.com/prisma/prisma/pull/28159). -- Fixed JSON column handling when using a MariaDB database. Learn more in this [PR](https://github.com/prisma/prisma/pull/28211). + Learn more in this [PR](https://github.com/prisma/orm/pull/28156/files#diff-351f5d894309f058776099c378e3956271f34f34c04e2b54576045b9773ab61aR61-R62). +- Relaxed the support package range for `@opentelemetry/instrumentation` to be compatible with `">=0.52.0 <1"`. Learn more in this [PR](https://github.com/prisma/orm/pull/28199/files). +- Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this [PR](https://github.com/prisma/orm/pull/28159). +- Fixed JSON column handling when using a MariaDB database. Learn more in this [PR](https://github.com/prisma/orm/pull/28211). - Restored the original behaviour of group-by aggregations where they would refer to columns with explicit table names which fixes a regression that would result in ambiguous column errors. Learn more in this [PR](https://github.com/prisma/prisma-engines/pull/5629). ## Preparing for the future of Prisma ORM @@ -145,7 +145,7 @@ export default defineConfig({ ``` For a full reference of the options that can be used in Prisma Config, see the [docs](https://www.prisma.io/docs/orm/v7/reference/prisma-config-reference). -> **Note**: When using Prisma Config, [automatic loading](https://github.com/prisma/prisma/issues/15620) of env vars is disabled. This means you need to [manually load env vars](https://www.prisma.io/docs/orm/v7/reference/prisma-config-reference#using-environment-variables), e.g. using `dotenv`. +> **Note**: When using Prisma Config, [automatic loading](https://github.com/prisma/orm/issues/15620) of env vars is disabled. This means you need to [manually load env vars](https://www.prisma.io/docs/orm/v7/reference/prisma-config-reference#using-environment-variables), e.g. using `dotenv`. ## Try it out and share your feedback diff --git a/apps/blog/content/blog/performance-benchmarks-comparing-query-latency-across-typescript-orms-and-databases/index.mdx b/apps/blog/content/blog/performance-benchmarks-comparing-query-latency-across-typescript-orms-and-databases/index.mdx index 0386d80012..941e80b7b2 100644 --- a/apps/blog/content/blog/performance-benchmarks-comparing-query-latency-across-typescript-orms-and-databases/index.mdx +++ b/apps/blog/content/blog/performance-benchmarks-comparing-query-latency-across-typescript-orms-and-databases/index.mdx @@ -213,7 +213,7 @@ In the end, much of an application's performance depends on the developer's abil ## Improve the performance of your Prisma ORM queries -Performance plays a crucial role for us at Prisma and we have focused _a lot_ recently on improving various aspects of Prisma ORM in that area, e.g. by introducing the option to use [DB-level JOINs](https://www.prisma.io/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview), implementing [many performance improvements in `v5`](https://www.prisma.io/blog/prisma-5-f66prwkjx72s), improving [serverless cold starts by 9x](https://www.prisma.io/blog/prisma-and-serverless-73hbgKnZ6t) or increasing the speed of `$queryRaw` by 2x in the last [`5.17.0`](https://github.com/prisma/prisma/releases/) release. +Performance plays a crucial role for us at Prisma and we have focused _a lot_ recently on improving various aspects of Prisma ORM in that area, e.g. by introducing the option to use [DB-level JOINs](https://www.prisma.io/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview), implementing [many performance improvements in `v5`](https://www.prisma.io/blog/prisma-5-f66prwkjx72s), improving [serverless cold starts by 9x](https://www.prisma.io/blog/prisma-and-serverless-73hbgKnZ6t) or increasing the speed of `$queryRaw` by 2x in the last [`5.17.0`](https://github.com/prisma/orm/releases/) release. ### Performance checklist for Prisma ORM @@ -227,7 +227,7 @@ Here's a basic checklist that helps you ensure that your Prisma ORM queries are - Add a caching layer to your DB (e.g. [Prisma Accelerate](https://www.prisma.io/data-platform/accelerate)). - If your app is serverless, follow the [best practices for serverless performance](https://www.prisma.io/blog/how-to-improve-startup-times-kdRB9MjPEv). -If you follow these recommendations but are still seeing slow queries, please [open an issue on GitHub](https://github.com/prisma/prisma/issues/) with details about your query so that we can make sure it's as fast as it should be! +If you follow these recommendations but are still seeing slow queries, please [open an issue on GitHub](https://github.com/prisma/orm/issues/) with details about your query so that we can make sure it's as fast as it should be! ### Insights and recommendations with Prisma Optimize diff --git a/apps/blog/content/blog/prisma-2-beta-b7bcl0gd8d8e/index.mdx b/apps/blog/content/blog/prisma-2-beta-b7bcl0gd8d8e/index.mdx index 4c824416de..be4e695698 100644 --- a/apps/blog/content/blog/prisma-2-beta-b7bcl0gd8d8e/index.mdx +++ b/apps/blog/content/blog/prisma-2-beta-b7bcl0gd8d8e/index.mdx @@ -158,7 +158,7 @@ The Prisma 2.0 Beta comes with the following tools: Try the new Prisma Client in 5 minutes by following the [**Quickstart**](https://www.prisma.io/docs/getting-started/quickstart) in the new docs. -> **Note**: Learn more about the Beta release in the [release notes](https://github.com/prisma/prisma/releases/tag/2.0.0-beta.1). +> **Note**: Learn more about the Beta release in the [release notes](https://github.com/prisma/orm/releases/tag/2.0.0-beta.1). ## Renaming the `prisma2` repository to `prisma` @@ -166,7 +166,7 @@ Since its initial release, the main repository for Prisma 2.0 has been called `p Because Prisma 2.0 is now the default for developers getting started with Prisma, the Prisma repositories have been renamed as follows: -- The `prisma/prisma2` repository has been renamed to [`prisma/prisma`](https://github.com/prisma/prisma/) +- The `prisma/prisma2` repository has been renamed to [`prisma/prisma`](https://github.com/prisma/orm/) - The `prisma/prisma` repository has been renamed to [`prisma/prisma1`](https://github.com/prisma/prisma1/) ## Renaming the `prisma2` CLI @@ -248,7 +248,7 @@ The Prisma 1 examples have been moved to the [`prisma1-examples`](https://github Whether or not you should upgrade depends on the context of your project. In general, one major consideration is the fact that Prisma Migrate is still experimental. This means you probably need to make any future adjustments to your database schema using SQL or another migration tool. -Also, note that we will put together an [upgrade guide as well as dedicated tooling](https://github.com/prisma/prisma/issues/1937) for the upgrade process over the next weeks. So, if you do want to upgrade despite Prisma Migrate not being ready, it might be worth waiting until these resources are in place. +Also, note that we will put together an [upgrade guide as well as dedicated tooling](https://github.com/prisma/orm/issues/1937) for the upgrade process over the next weeks. So, if you do want to upgrade despite Prisma Migrate not being ready, it might be worth waiting until these resources are in place. @@ -316,5 +316,5 @@ We are really excited to finally share the Beta version of Prisma 2.0 and can't
[Get started with Prisma 2.0](https://www.prisma.io/docs/getting-started/quickstart) -If you want to leave feedback, share ideas, create feature requests or submit bug reports, please do so in the (renamed) [`prisma`](https://github.com/prisma/prisma) repository on GitHub and join the (renamed) [`#prisma2-beta`](https://app.slack.com/client/T0MQBS8JG/CKQTGR6T0) channel on the [Prisma Slack](https://slack.prisma.io)! +If you want to leave feedback, share ideas, create feature requests or submit bug reports, please do so in the (renamed) [`prisma`](https://github.com/prisma/orm) repository on GitHub and join the (renamed) [`#prisma2-beta`](https://app.slack.com/client/T0MQBS8JG/CKQTGR6T0) channel on the [Prisma Slack](https://slack.prisma.io)! diff --git a/apps/blog/content/blog/prisma-5-f66prwkjx72s/index.mdx b/apps/blog/content/blog/prisma-5-f66prwkjx72s/index.mdx index 5bf13a44d4..ae28f179d0 100644 --- a/apps/blog/content/blog/prisma-5-f66prwkjx72s/index.mdx +++ b/apps/blog/content/blog/prisma-5-f66prwkjx72s/index.mdx @@ -14,11 +14,11 @@ tags: - "orm" --- -[Prisma 5](https://github.com/prisma/prisma/releases/tag/5.0.0) introduces changes that make it significantly faster. These changes especially improve the experience of using Prisma in serverless environments thanks to a new and more efficient [JSON-based wire protocol](/prisma-and-serverless-73hbgKnZ6t) that Prisma Client uses under the hood. +[Prisma 5](https://github.com/prisma/orm/releases/tag/5.0.0) introduces changes that make it significantly faster. These changes especially improve the experience of using Prisma in serverless environments thanks to a new and more efficient [JSON-based wire protocol](/prisma-and-serverless-73hbgKnZ6t) that Prisma Client uses under the hood. ## Improved startup performance in Prisma Client -From Prisma [4.8.0](https://github.com/prisma/prisma/releases/tag/4.8.0), we have doubled down on our efforts to improve Prisma's performance and developer experience. In particular, we focused on improving Prisma's startup performance in serverless environments. +From Prisma [4.8.0](https://github.com/prisma/orm/releases/tag/4.8.0), we have doubled down on our efforts to improve Prisma's performance and developer experience. In particular, we focused on improving Prisma's startup performance in serverless environments. In our quest to improve Prisma's performance, we unearthed a few inefficiencies, which we tackled. @@ -44,7 +44,7 @@ Prior to Prisma 4.11.0, Prisma used a GraphQL-like protocol to communicate betwe During our performance exploration, we noticed that the current implementation added a considerable CPU and memory overhead, especially for larger schemas. -One of our solutions to alleviate this issue was a complete redesign of our wire protocol. Using JSON, we were able to make communication between Prisma Client and the query engine significantly more efficient. We released this feature behind the `jsonProtocol` Preview feature flag in version [4.11.0](https://github.com/prisma/prisma/releases/tag/4.11.0). +One of our solutions to alleviate this issue was a complete redesign of our wire protocol. Using JSON, we were able to make communication between Prisma Client and the query engine significantly more efficient. We released this feature behind the `jsonProtocol` Preview feature flag in version [4.11.0](https://github.com/prisma/orm/releases/tag/4.11.0). Before we began any work on performance improvements, an average "cold start" request looked like this: @@ -100,8 +100,8 @@ The following graph shows Prisma Client's performance after we optimized its int ## Try out Prisma 5 and share your feedback -We encourage you to upgrade to Prisma [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) and are looking forward to hearing your feedback! 🎉 +We encourage you to upgrade to Prisma [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) and are looking forward to hearing your feedback! 🎉 -Prisma 5 is a major version increment, and it comes with a few breaking changes. We expect only a few users will be affected by the changes. However, before upgrading, we recommend that you check out our [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-5) to understand the impact on your application. If you run into any bugs, please submit an [issue](https://github.com/prisma/prisma/issues), or upvote a corresponding issue if it already exists. +Prisma 5 is a major version increment, and it comes with a few breaking changes. We expect only a few users will be affected by the changes. However, before upgrading, we recommend that you check out our [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-5) to understand the impact on your application. If you run into any bugs, please submit an [issue](https://github.com/prisma/orm/issues), or upvote a corresponding issue if it already exists. We are committed to improving Prisma's overall performance and will continue shipping improvements that address performance-related issues. Be sure to [follow us on X/Twitter](https://pris.ly/x) not to miss any updates! diff --git a/apps/blog/content/blog/prisma-6-9-0-release/index.mdx b/apps/blog/content/blog/prisma-6-9-0-release/index.mdx index a8906a1981..12d81c8785 100644 --- a/apps/blog/content/blog/prisma-6-9-0-release/index.mdx +++ b/apps/blog/content/blog/prisma-6-9-0-release/index.mdx @@ -17,7 +17,7 @@ You can now connect to Prisma Postgres with any DB library (e.g. Kysely or Drizz ### TL;DR: The Rust-Free ORM is ready for production-use -Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/prisma/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. +Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/orm/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. - **No binary overhead:** The dependency on native Rust binaries is eliminated, drastically simplifying deployment and reducing potential complexity issues. - **Performance:** Get **up to 3.4x faster queries** (by removing cross-language serialization) and a **90% smaller bundle size** (from ~14MB to 1.6 MB). diff --git a/apps/blog/content/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql/index.mdx b/apps/blog/content/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql/index.mdx index 61ce815763..712a6e3672 100644 --- a/apps/blog/content/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql/index.mdx +++ b/apps/blog/content/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql/index.mdx @@ -14,7 +14,7 @@ heroImagePath: "/prisma-6-better-performance-more-flexibility-and-type-safe-sql/ Looking for the newest performance numbers? We've benchmarked [Prisma 8](https://pris.ly/pn-series), the new TypeScript-first foundation for Prisma ORM: about 87% of the raw `pg` driver's peak throughput and 52% more requests per second than Prisma 7. [See the latest results](/prisma-next-performance-benchmark). :::: -Today, we are releasing [Prisma v6](https://github.com/prisma/prisma/releases/tag/6.0.0)! Since the last major version, we have been hard at work incorporating user feedback, making Prisma ORM faster and more flexible, and adding amazing features like type-safe raw SQL queries. +Today, we are releasing [Prisma v6](https://github.com/prisma/orm/releases/tag/6.0.0)! Since the last major version, we have been hard at work incorporating user feedback, making Prisma ORM faster and more flexible, and adding amazing features like type-safe raw SQL queries. ## Prisma v6: What you need to know @@ -36,7 +36,7 @@ In principle, there are two different approaches when you need to query data fro - **Database-level**: Send a single query to the database using the SQL `JOIN` keyword and let the data be _joined_ by the database directly. - **Application-level**: Send multiple queries to individual tables to the database and _join_ the data yourself in your application. -Depending on your use case, your database schema, and several other factors, one strategy may be more appropriate than the other. Up until Prisma ORM [v5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0), Prisma ORM would always use the application-level JOIN strategy. +Depending on your use case, your database schema, and several other factors, one strategy may be more appropriate than the other. Up until Prisma ORM [v5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0), Prisma ORM would always use the application-level JOIN strategy. However, with the v5.7.0 release, we now allow you to pick the best JOIN strategy for your use case, ensuring you can always get the best performance for your queries. To choose a join strategy, you can use the `relationLoadStrategy` option on relation queries, e.g.: @@ -67,11 +67,11 @@ const user = await prisma.user.update({ }, }) ``` -In versions before [v5.11.0](https://github.com/prisma/prisma/releases/tag/5.11.0), Prisma ORM would translate this into multiple SQL `INSERT` queries, each requiring its own round-trip to the database. As of this release, these nested `create` queries are optimized and the `INSERT` queries are sent to the database _in bulk_ in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations. +In versions before [v5.11.0](https://github.com/prisma/orm/releases/tag/5.11.0), Prisma ORM would translate this into multiple SQL `INSERT` queries, each requiring its own round-trip to the database. As of this release, these nested `create` queries are optimized and the `INSERT` queries are sent to the database _in bulk_ in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations. ### Faster queries in almost every release since v5 -If you go through Prisma ORM [releases](https://github.com/prisma/prisma/releases/) on GitHub, you'll find that almost every release came with some kind of performance improvements. +If you go through Prisma ORM [releases](https://github.com/prisma/orm/releases/) on GitHub, you'll find that almost every release came with some kind of performance improvements. We're committed to continue our investment in query performance to ensure your queries are as fast as possible 💚 By the way, if you're curious to learn how Prisma ORM compares to other TypeScript ORMs in terms of performance, check out our [TypeScript ORM benchmarks](https://www.prisma.io/blog/performance-benchmarks-comparing-query-latency-across-typescript-orms-and-databases). @@ -83,7 +83,7 @@ Over the past year, we not only improved performance, but also made Prisma ORM a Both [PlanetScale](https://planetscale.com/docs/tutorials/planetscale-serverless-driver) and [Neon](https://neon.tech/docs/serverless/serverless-driver) have released _serverless drivers_ that enable accessing their database instances via HTTP (instead of TCP, which is commonly used for database connections). These serverless drivers are particularly useful in serverless and edge environments, where initiating a TCP connection may be too expensive or entirely impossible. -In [v5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0), we released [support for custom database drivers in Prisma ORM](https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV), enabling the use of both the PlanetScale and Neon serverless drivers. Here's an example for connecting to a PlanetScale instance using their serverless driver: +In [v5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0), we released [support for custom database drivers in Prisma ORM](https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV), enabling the use of both the PlanetScale and Neon serverless drivers. Here's an example for connecting to a PlanetScale instance using their serverless driver: ```ts import { connect } from '@planetscale/database'; @@ -100,7 +100,7 @@ Edge functions, such as Cloudflare Workers or Vercel Edge Functions, have been r ![](/prisma-6-better-performance-more-flexibility-and-type-safe-sql/imgs/cdc1687a8bc84dd978cd3e2270618719a6da7207-1920x1080.png) -Since [v5.11.0](https://github.com/prisma/prisma/releases/tag/5.11.0), Prisma ORM can be used in these edge environments. This has been a major achievement and we're excited to see what developers are building with Prisma ORM at the edge! +Since [v5.11.0](https://github.com/prisma/orm/releases/tag/5.11.0), Prisma ORM can be used in these edge environments. This has been a major achievement and we're excited to see what developers are building with Prisma ORM at the edge! You can learn more about this feature in this blog post: [Prisma ORM Support for Edge Functions is Now in Preview](https://www.prisma.io/blog/prisma-orm-support-for-edge-functions-is-now-in-preview). @@ -112,7 +112,7 @@ Both databases are based on SQLite and well-suited for building applications at ### Split your Prisma schema into multiple files -In [v5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0), we tackled a popular feature request and made it possible to have _multiple_ files that make up your Prisma schema. For example, you can now have these two files that each contain a single model: +In [v5.15.0](https://github.com/prisma/orm/releases/tag/5.15.0), we tackled a popular feature request and made it possible to have _multiple_ files that make up your Prisma schema. For example, you can now have these two files that each contain a single model: #### `user.prisma` diff --git a/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx b/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx index 7bf355073f..566e296b6d 100644 --- a/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx +++ b/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx @@ -41,7 +41,7 @@ That shift trades peak parallelism for: So if your workload is data-heavy or raw-SQL-heavy, Prisma 7 often wins. If your workload previously benefited from Rust-level threading, you may see parity or regressions. -This was a deliberate trade-off, not an oversight. We’re continuing to improve performance in Prisma 7, as seen in [the 7.3.0 release](https://github.com/prisma/prisma/releases/tag/7.3.0), with more incremental improvements on the way. +This was a deliberate trade-off, not an oversight. We’re continuing to improve performance in Prisma 7, as seen in [the 7.3.0 release](https://github.com/prisma/orm/releases/tag/7.3.0), with more incremental improvements on the way. ### Does Prisma 7 support MongoDB and other databases? diff --git a/apps/blog/content/blog/prisma-7-performance-benchmarks/index.mdx b/apps/blog/content/blog/prisma-7-performance-benchmarks/index.mdx index 43022c632c..88f922193d 100644 --- a/apps/blog/content/blog/prisma-7-performance-benchmarks/index.mdx +++ b/apps/blog/content/blog/prisma-7-performance-benchmarks/index.mdx @@ -24,7 +24,7 @@ The most common question we have seen is simple: > *“Why does Prisma 7 feel slower than Prisma 6?”* -Some benchmarks show Prisma 7 running slower than other ORMs and even slower than Prisma 6 in some cases. If you have seen only those graphs, the confusion is understandable. We have reviewed every issue, comment, and benchmark the community shared. The [most referenced one is here](https://github.com/prisma/prisma/issues/28845). It is a detailed test suite that compares Prisma 6 and Prisma 7. In those tests, Prisma 7 fall behind. +Some benchmarks show Prisma 7 running slower than other ORMs and even slower than Prisma 6 in some cases. If you have seen only those graphs, the confusion is understandable. We have reviewed every issue, comment, and benchmark the community shared. The [most referenced one is here](https://github.com/prisma/orm/issues/28845). It is a detailed test suite that compares Prisma 6 and Prisma 7. In those tests, Prisma 7 fall behind. But before drawing conclusions, we need to look at what these tests are actually measuring. diff --git a/apps/blog/content/blog/prisma-adopts-semver-strictly/index.mdx b/apps/blog/content/blog/prisma-adopts-semver-strictly/index.mdx index a14be23eee..fe0e2f4f8b 100644 --- a/apps/blog/content/blog/prisma-adopts-semver-strictly/index.mdx +++ b/apps/blog/content/blog/prisma-adopts-semver-strictly/index.mdx @@ -55,7 +55,7 @@ As we're seeing more developers and companies adopt Prisma and getting helpful f ## One of Prisma's upcoming releases will have breaking changes -One of the upcoming Prisma [releases](https://github.com/prisma/prisma) will come with breaking changes. Following our new release strategy, the _major_ version number will be incremented, and Prisma's new version will therefore be `3.x.x`. +One of the upcoming Prisma [releases](https://github.com/prisma/orm) will come with breaking changes. Following our new release strategy, the _major_ version number will be incremented, and Prisma's new version will therefore be `3.x.x`. You can read more about our release strategy in the [documentation](https://www.prisma.io/docs/about/prisma/releases). diff --git a/apps/blog/content/blog/prisma-and-serverless-73hbgKnZ6t/index.mdx b/apps/blog/content/blog/prisma-and-serverless-73hbgKnZ6t/index.mdx index e73fbca7fd..1a7aa11d4e 100644 --- a/apps/blog/content/blog/prisma-and-serverless-73hbgKnZ6t/index.mdx +++ b/apps/blog/content/blog/prisma-and-serverless-73hbgKnZ6t/index.mdx @@ -204,13 +204,13 @@ After redesigning the wire protocol, we effectively removed the entire -> **Note**: You can check out pull requests [prisma-engines#3624](https://github.com/prisma/prisma-engines/pull/3624) and [prisma#17911](https://github.com/prisma/prisma/pull/17911) with the actual changes made if you are interested. +> **Note**: You can check out pull requests [prisma-engines#3624](https://github.com/prisma/prisma-engines/pull/3624) and [prisma#17911](https://github.com/prisma/orm/pull/17911) with the actual changes made if you are interested. -Check out this amazing feedback on [GitHub](https://github.com/prisma/prisma/issues/18095) from users who tried out the new JSON-based wire protocol: +Check out this amazing feedback on [GitHub](https://github.com/prisma/orm/issues/18095) from users who tried out the new JSON-based wire protocol: -> **Note**: The JSON-based wire protocol is currently in [Preview](https://www.prisma.io/docs/about/prisma/releases#preview). Once it's ready for production, it will become the default for how Prisma Client communicates with the query engine. Please give it a try and [submit any feedback](https://github.com/prisma/prisma/issues/18095) to help speed up the process of making this feature generally available. +> **Note**: The JSON-based wire protocol is currently in [Preview](https://www.prisma.io/docs/about/prisma/releases#preview). Once it's ready for production, it will become the default for how Prisma Client communicates with the query engine. Please give it a try and [submit any feedback](https://github.com/prisma/orm/issues/18095) to help speed up the process of making this feature generally available. ### Host your function in the same region as your database @@ -272,7 +272,7 @@ Notice the segment is significantly shorter. ### Various small wins -Along the way, we also found many smaller inefficiencies that we were able to improve. There were a lot of these, so we won't go over each one, but a good example is an optimization we made to our platform detection routine used to search for the OpenSSL library on Linux environments (the pull request for that enhancement can be found [here](https://github.com/prisma/prisma/pull/18638)). +Along the way, we also found many smaller inefficiencies that we were able to improve. There were a lot of these, so we won't go over each one, but a good example is an optimization we made to our platform detection routine used to search for the OpenSSL library on Linux environments (the pull request for that enhancement can be found [here](https://github.com/prisma/orm/pull/18638)). This enhancement shaves ~10-20ms off the cold start on average. While that doesn't seem like much, the accumulation of this enhancement and other small enhancements we made add up to another good chunk of saved time. @@ -314,8 +314,8 @@ We invite you to help improve the performance of Prisma Client, specifically in There are many ways you can contribute to this goal of providing a world-class ORM that is accessible in serverless environments and on the edge: -- Submit [issues](https://github.com/prisma/prisma/issues) you find when working with Prisma on serverless. -- Have an idea how we might improve? Start a [discussion](https://github.com/prisma/prisma/discussions)! -- Try out the `jsonProtocol` preview feature and provide [feedback](https://github.com/prisma/prisma/issues/18095). +- Submit [issues](https://github.com/prisma/orm/issues) you find when working with Prisma on serverless. +- Have an idea how we might improve? Start a [discussion](https://github.com/prisma/orm/discussions)! +- Try out the `jsonProtocol` preview feature and provide [feedback](https://github.com/prisma/orm/issues/18095). Prisma ORM is an open source project, and as such we fully understand the importance of community feedback and participation. We love feedback, critiques, questions and anything that might help push Prisma forward for the good of every developer. diff --git a/apps/blog/content/blog/prisma-microsoft-sql-server-azure-sql-production-ga/index.mdx b/apps/blog/content/blog/prisma-microsoft-sql-server-azure-sql-production-ga/index.mdx index 82ba55642b..eaaad93b56 100644 --- a/apps/blog/content/blog/prisma-microsoft-sql-server-azure-sql-production-ga/index.mdx +++ b/apps/blog/content/blog/prisma-microsoft-sql-server-azure-sql-production-ga/index.mdx @@ -28,7 +28,7 @@ Today we are excited to announce that Prisma support for SQL Server and Azure SQ ## Support for SQL Server and Azure SQL in Prisma is Generally Available -Today we are excited to announce that Prisma support for SQL Server and Azure SQL is Generally Available and ready for production workloads as part of the [3.0.1 release](https://github.com/prisma/prisma/releases/tag/3.0.1)! 🎉 +Today we are excited to announce that Prisma support for SQL Server and Azure SQL is Generally Available and ready for production workloads as part of the [3.0.1 release](https://github.com/prisma/orm/releases/tag/3.0.1)! 🎉 Since we released Prisma Client for General Availability over a year ago with support for PostgreSQL, MySQL, SQLite, and MariaDB, we've heard from thousands of engineers about how the Prisma ORM is helping them be more productive and confident when building data-intensive applications. @@ -67,7 +67,7 @@ There are three core concepts central to the development workflow with Prisma: - Fully typed TypeScript database client - SQL migrations based on changes in the Prisma schema. -Today's [release](https://github.com/prisma/prisma/releases/tag/3.0.1) brings Prisma support for Microsoft SQL Server and Azure SQL to General Availability. We couldn't be more excited to welcome new developers to the Prisma community so that you can reap the benefits of productivity and confidence. +Today's [release](https://github.com/prisma/orm/releases/tag/3.0.1) brings Prisma support for Microsoft SQL Server and Azure SQL to General Availability. We couldn't be more excited to welcome new developers to the Prisma community so that you can reap the benefits of productivity and confidence. {/* @@ -124,7 +124,7 @@ Finally, check out our [**Azure Functions** deployment guide](https://www.prisma If you are using Microsoft SQL Server or Azure SQL today, you can try out Prisma with your existing database in 15 minutes by following [this guide](https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-sqlserver?utm_source=blog&utm_medium=blog&utm_campaign=sqlserver-ga). -If you've been using the SQL Server and Azure SQL connector while it was in Preview in versions prior to [`3.0.1`](https://github.com/prisma/prisma/releases/tag/3.0.1), check out the Breaking Changes section in the [release notes](https://github.com/prisma/prisma/releases/tag/3.0.1) for more details about upgrading. +If you've been using the SQL Server and Azure SQL connector while it was in Preview in versions prior to [`3.0.1`](https://github.com/prisma/orm/releases/tag/3.0.1), check out the Breaking Changes section in the [release notes](https://github.com/prisma/orm/releases/tag/3.0.1) for more details about upgrading. You can also remove the `microsoftSqlServer` flag from `previewFeatures` in your Prisma Schema. diff --git a/apps/blog/content/blog/prisma-migrate-dx-primitives/index.mdx b/apps/blog/content/blog/prisma-migrate-dx-primitives/index.mdx index ca6189f4ac..c2f93e999c 100644 --- a/apps/blog/content/blog/prisma-migrate-dx-primitives/index.mdx +++ b/apps/blog/content/blog/prisma-migrate-dx-primitives/index.mdx @@ -22,7 +22,7 @@ Prisma Migrate is a database schema migration tool that simplifies evolving the ## Better DX for troubleshooting schema migrations -We are excited to launch two new low-level Migrate commands in Preview: `migrate diff` and `db execute` as part of the [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) release of Prisma. +We are excited to launch two new low-level Migrate commands in Preview: `migrate diff` and `db execute` as part of the [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) release of Prisma. The two commands are very versatile — they can be used to troubleshoot and resolve failed schema migrations and get quick feedback about schema-related discrepancies between environments, branches, and representations (Prisma data model, migration history, database schema). @@ -140,8 +140,8 @@ The new commands are versatile tools for schema migrations. But many established ## Try the new Migrate commands and share your feedback -We built the new commands for you and are keen to [hear your feedback](https://github.com/prisma/prisma/issues/11514). +We built the new commands for you and are keen to [hear your feedback](https://github.com/prisma/orm/issues/11514). -🐛 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/prisma/issues/new/choose) so we can look into it. +🐛 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/orm/issues/new/choose) so we can look into it. 👷‍♀️ We are thrilled to share the Preview version of the new Migrate commands and looking forward to your feedback. diff --git a/apps/blog/content/blog/prisma-migrate-ga-b5eno5g08d0b/index.mdx b/apps/blog/content/blog/prisma-migrate-ga-b5eno5g08d0b/index.mdx index 4c52a3bc1d..f6c5c6494f 100644 --- a/apps/blog/content/blog/prisma-migrate-ga-b5eno5g08d0b/index.mdx +++ b/apps/blog/content/blog/prisma-migrate-ga-b5eno5g08d0b/index.mdx @@ -296,7 +296,7 @@ For example, we'll be [improving the handling of column renames in Prisma Migrat Beyond that, the following roadmap items will introduce further improvements to the general management of database schemas: - Stabilize and promote [`prisma db push`](https://www.notion.so/prismaio/Simplify-database-migrations-during-prototyping-2f24abdd283c46f79c688a7cd99fc0b6) and [`prisma db seed`](https://www.notion.so/prismaio/Database-Seeding-ea7a86c183c949b7b3fea1658ed8c179) to General Availability. - [Improve environment management configuration.](https://www.notion.so/prismaio/Improve-environment-management-and-Prisma-level-configuration-7dc7c0063fee49c4857ed9b2276c096a) -- [Add support for configuring cascading deletes in the Prisma schema.](https://github.com/prisma/prisma/issues/2810) +- [Add support for configuring cascading deletes in the Prisma schema.](https://github.com/prisma/orm/issues/2810) --- diff --git a/apps/blog/content/blog/prisma-migrate-preview-b5eno5g08d0b/index.mdx b/apps/blog/content/blog/prisma-migrate-preview-b5eno5g08d0b/index.mdx index 4e5555ca32..45512ef94c 100644 --- a/apps/blog/content/blog/prisma-migrate-preview-b5eno5g08d0b/index.mdx +++ b/apps/blog/content/blog/prisma-migrate-preview-b5eno5g08d0b/index.mdx @@ -45,7 +45,7 @@ Prisma Migrate integrates with Prisma Client using the Prisma schema as their sh Prisma Migrate has passed rigorous testing internally and is now ready for broader testing by the community. You can use it with PostgreSQL, MySQL, SQLite, and SQL Server. **However, as a Preview feature, it is not fully production-ready yet.** To read more about what Preview means, check out the [maturity levels](https://www.prisma.io/docs/about/prisma/releases#preview) in the Prisma docs. -Thus, we're inviting you to try it out and [give us feedback](https://github.com/prisma/prisma/issues/4531) so we can bring Prisma Migrate to General Availability. 🚢 +Thus, we're inviting you to try it out and [give us feedback](https://github.com/prisma/orm/issues/4531) so we can bring Prisma Migrate to General Availability. 🚢 Your feedback and suggestions will help us shape the future of Prisma Migrate. 🙌 @@ -167,7 +167,7 @@ One of the most requested features in Prisma is support for the database's nativ Currently, the Prisma schema can only represent a limited set of types: `String`, `Int`, `Float`, `Boolean`, `DateTime`, and `Json`. Each of these types has a default mapping to an underlying database type that's specified for each database connector (see the mappings for [PostgreSQL](https://www.prisma.io/docs/concepts/database-connectors/postgresql#prisma-migrate) and [MySQL](https://www.prisma.io/docs/concepts/database-connectors/mysql#prisma-migrate)). -In version [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0), we released the `nativeTypes` Preview feature – the ability to annotate fields in the Prisma schema with the specific native database type that it should be mapped to. **However, the native types preview feature doesn't work with Prisma Migrate yet**. +In version [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0), we released the `nativeTypes` Preview feature – the ability to annotate fields in the Prisma schema with the specific native database type that it should be mapped to. **However, the native types preview feature doesn't work with Prisma Migrate yet**. Even so, you can still change the types of columns in the generated SQL as long as they are supported, as documented in the [PostgreSQL](https://www.prisma.io/docs/concepts/database-connectors/postgresql#prisma-migrate) and [MySQL](https://www.prisma.io/docs/concepts/database-connectors/mysql#prisma-migrate) connector docs. @@ -179,9 +179,9 @@ We built Prisma Migrate for you and are keen to hear your feedback. We want to understand how Prisma Migrate fits into your development workflow and how we can help you stay productive and confident while building and evolving data-centric applications. -🐛 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/prisma/issues/new/choose) so we can look into it. +🐛 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/orm/issues/new/choose) so we can look into it. -🏗 Share your feedback about how the new Prisma Migrate is working out for you on [GitHub](https://github.com/prisma/prisma/issues/4531). +🏗 Share your feedback about how the new Prisma Migrate is working out for you on [GitHub](https://github.com/prisma/orm/issues/4531). 🌍 Join us on our [Slack](https://slack.prisma.io) in the [`#prisma-migrate`](https://app.slack.com/client/T0MQBS8JG/C01ACF1DJ1M) channel for help. diff --git a/apps/blog/content/blog/prisma-mongodb-preview-release/index.mdx b/apps/blog/content/blog/prisma-mongodb-preview-release/index.mdx index 2985d47d8c..7a9ada7646 100644 --- a/apps/blog/content/blog/prisma-mongodb-preview-release/index.mdx +++ b/apps/blog/content/blog/prisma-mongodb-preview-release/index.mdx @@ -26,7 +26,7 @@ Today we are excited to expand the range of supported databases with preview sup ## TL;DR -- Prisma release [2.27.0](https://github.com/prisma/prisma/releases/tag/2.27.0) adds [Preview support](https://www.prisma.io/docs/orm/v7/more/releases#preview) for MongoDB. +- Prisma release [2.27.0](https://github.com/prisma/orm/releases/tag/2.27.0) adds [Preview support](https://www.prisma.io/docs/orm/v7/more/releases#preview) for MongoDB. - Prisma introduces a schema to MongoDB from which Prisma Client is generated, giving you the power of type safety in your queries. - Check out the [**Start from scratch guide**](https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch/mongodb-typescript-mongodb) in the docs. - This is a preview release, so there may be bugs and breaking changes. Try it out and share your feedback @@ -37,7 +37,7 @@ Watch the getting started video: [**MongoDB with Prisma**](https://www.youtube.c ## Adding MongoDB support to Prisma -MongoDB has been [our most requested feature since the release of Prisma 2](https://github.com/prisma/prisma/issues/1277). Today we're thrilled to announce Preview support for MongoDB in Prisma! 🎉 +MongoDB has been [our most requested feature since the release of Prisma 2](https://github.com/prisma/orm/issues/1277). Today we're thrilled to announce Preview support for MongoDB in Prisma! 🎉 Earlier this year, we released an Early Access of the MongoDB connector to Prisma Client. Since then, hundreds of engineers signed up for the Early Access program and provided us with helpful feedback. @@ -45,7 +45,7 @@ This release marks a significant milestone in bringing the benefits of Prisma to MongoDB support has passed rigorous testing internally and by the Early Access participants and is now ready for broader testing by the community. **However, as a Preview feature, it is not production-ready.** To read more about what preview means, check out the [maturity levels](https://www.prisma.io/docs/orm/v7/more/releases#preview) in the Prisma docs. -Thus, we're inviting the MongoDB community to try it out and [give us feedback](https://github.com/prisma/prisma/issues/8241) so we can bring MongoDB support to general availability. 🚀 +Thus, we're inviting the MongoDB community to try it out and [give us feedback](https://github.com/prisma/orm/issues/8241) so we can bring MongoDB support to general availability. 🚀 ## Making MongoDB type safe with Prisma @@ -76,17 +76,17 @@ You can also dig into our ready-to-run [example](https://github.com/prisma/prism Support for MongoDB comes with some limitations that are detailed in this section. -- [MongoDB replica set is required for transactions](https://github.com/prisma/prisma/issues/8266) -- [Prisma Migrate is not supported yet](https://github.com/prisma/prisma/issues/7305) -- [Introspection is not supported](https://github.com/prisma/prisma/issues/6787) -- [Unique indices need to be created manually](https://github.com/prisma/prisma/issues/6727) -- [Limited support for embedded documents (currently only possible with the Json type)](https://github.com/prisma/prisma/issues/6708) +- [MongoDB replica set is required for transactions](https://github.com/prisma/orm/issues/8266) +- [Prisma Migrate is not supported yet](https://github.com/prisma/orm/issues/7305) +- [Introspection is not supported](https://github.com/prisma/orm/issues/6787) +- [Unique indices need to be created manually](https://github.com/prisma/orm/issues/6727) +- [Limited support for embedded documents (currently only possible with the Json type)](https://github.com/prisma/orm/issues/6708) ## Try Prisma with MongoDB and share your feedback We built this for you and are eager to hear your feedback! -🐜 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/prisma/issues/new/choose) so we can look into it. +🐜 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/orm/issues/new/choose) so we can look into it. 💡 Are you interested in learning more about MongoDB? Check out the [MongoDB section of Prisma's Data Guide](https://www.prisma.io/dataguide/mongodb). diff --git a/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx b/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx index e2092636d3..8118b489fb 100644 --- a/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx +++ b/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx @@ -53,7 +53,7 @@ Three extensions ship in the repo today, each demonstrating a different combinat ### pgvector: three layers in one pack -[@prisma/orm-extension-pgvector](https://github.com/prisma/prisma/tree/main/packages/3-extensions/pgvector) is the canonical example. It ships a `vector(N)` column type on the contract layer, `cosineDistance` and `cosineSimilarity` operators on the query layer, and the codec that maps the SQL `vector` type to `number[]` on the runtime layer. +[@prisma/orm-extension-pgvector](https://github.com/prisma/orm/tree/main/packages/3-extensions/pgvector) is the canonical example. It ships a `vector(N)` column type on the contract layer, `cosineDistance` and `cosineSimilarity` operators on the query layer, and the codec that maps the SQL `vector` type to `number[]` on the runtime layer. All three show up in the same project, file by file: @@ -90,13 +90,13 @@ const plan = sql ### arktype-json: codec and contract layers, library-author shape -[@prisma/orm-extension-arktype-json](https://github.com/prisma/prisma/tree/main/packages/3-extensions/arktype-json) is a per-library codec for JSON-with-schema columns. Pass it an arktype schema and you get back a typed JSON column whose TypeScript type matches the schema (`{ name: string; price: number }`) and whose values are validated against the schema on the wire. +[@prisma/orm-extension-arktype-json](https://github.com/prisma/orm/tree/main/packages/3-extensions/arktype-json) is a per-library codec for JSON-with-schema columns. Pass it an arktype schema and you get back a typed JSON column whose TypeScript type matches the schema (`{ name: string; price: number }`) and whose values are validated against the schema on the wire. The pattern is deliberately per-library: arktype-json today, `zod-json` and `valibot-json` on parallel tracks tomorrow, each shipping the same shape with their own serialize/rehydrate story. This is the natural template for the integration you've probably wanted: your TS library wired up at the contract layer, not bolted on around the edges of an ORM. ### ParadeDB: contract layer only -[@prisma/orm-extension-paradedb](https://github.com/prisma/prisma/tree/main/packages/3-extensions/paradedb) adds typed BM25 full-text-search index authoring for ParadeDB users: `bm25.text(...)`, `bm25.numeric(...)`, and `bm25Index({ ... })` with all twelve built-in tokenizers and validation against the BM25 contract. +[@prisma/orm-extension-paradedb](https://github.com/prisma/orm/tree/main/packages/3-extensions/paradedb) adds typed BM25 full-text-search index authoring for ParadeDB users: `bm25.text(...)`, `bm25.numeric(...)`, and `bm25Index({ ... })` with all twelve built-in tokenizers and validation against the BM25 contract. The query and migration layers for ParadeDB are explicitly planned, not yet shipped, and the README says so out loud. We think that's worth saying: an extension doesn't have to ship every layer at once. Authoring-first and following with the rest is a perfectly good trajectory, and the surface supports it. @@ -127,7 +127,7 @@ We, the Prisma 8 team, are available on Discord and eager to help you build, as ## The fastest way to start -Clone [`prisma/prisma`](https://github.com/prisma/prisma), point your coding agent at the repo, and tell it what you want to build. +Clone [`prisma/prisma`](https://github.com/prisma/orm), point your coding agent at the repo, and tell it what you want to build. The repo is dense with architecture docs, architecture decision record (ADRs), SPI READMEs, and reference extensions: enough context that an agent can absorb it in seconds and scaffold a working pack from your description alone, without you reading a line of it first. @@ -135,15 +135,15 @@ The result is normal TypeScript you can read, edit, and iterate on like any othe If you'd rather start from a known-good template yourself, pick the existing extension closest to what you want and copy it: -- **Building a feature pack with column types, operators, and codecs?** Copy [pgvector](https://github.com/prisma/prisma/tree/main/packages/3-extensions/pgvector) -- **Integrating a TypeScript library at the contract layer (validation, serialization, schema-driven types)?** Copy [arktype-json](https://github.com/prisma/prisma/tree/main/packages/3-extensions/arktype-json) -- **Adding typed authoring for a database feature, with the rest of the layers to follow later?** Copy [ParadeDB](https://github.com/prisma/prisma/tree/main/packages/3-extensions/paradedb) +- **Building a feature pack with column types, operators, and codecs?** Copy [pgvector](https://github.com/prisma/orm/tree/main/packages/3-extensions/pgvector) +- **Integrating a TypeScript library at the contract layer (validation, serialization, schema-driven types)?** Copy [arktype-json](https://github.com/prisma/orm/tree/main/packages/3-extensions/arktype-json) +- **Adding typed authoring for a database feature, with the rest of the layers to follow later?** Copy [ParadeDB](https://github.com/prisma/orm/tree/main/packages/3-extensions/paradedb) Either way, the packages are small. Reading code is faster than reading docs. ## Build an extension -Build it, then tell us about it in [`#prisma-next`](https://pris.ly/discord) on Discord, and star [`prisma/prisma`](https://github.com/prisma/prisma) on GitHub to follow the SPI as it matures. +Build it, then tell us about it in [`#prisma-next`](https://pris.ly/discord) on Discord, and star [`prisma/prisma`](https://github.com/prisma/orm) on GitHub to follow the SPI as it matures. Prisma 8 is early, and the SPI is stable enough that the existing extensions are real proof of what's possible, though we expect to iterate as more of you build against it. diff --git a/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx b/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx index 89839322c0..a636373fc9 100644 --- a/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx +++ b/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx @@ -218,11 +218,11 @@ Or ask your agent _anything_ about Prisma 8: > _"What happens if a migration fails during deployment?"_ > _"How do I handle breaking changes in my code?"_ -Once you've got something running, tag [us on X](https://pris.ly/x) and tell us what you built. The best community builds get a shout-out from the Prisma account and a link in the [Prisma 8 README](https://github.com/prisma/prisma). +Once you've got something running, tag [us on X](https://pris.ly/x) and tell us what you built. The best community builds get a shout-out from the Prisma account and a link in the [Prisma 8 README](https://github.com/prisma/orm). And when you're ready to ship it, our hosted database [Prisma Postgres](https://www.prisma.io/postgres) comes with a generous free tier. -Star and watch [prisma/prisma](https://github.com/prisma/prisma) on GitHub to follow what ships next. And if you hit a snag, start a thread in [#prisma-next](https://pris.ly/discord) on [our Discord](https://pris.ly/discord). +Star and watch [prisma/prisma](https://github.com/prisma/orm) on GitHub to follow what ships next. And if you hit a snag, start a thread in [#prisma-next](https://pris.ly/discord) on [our Discord](https://pris.ly/discord). We can't wait to see what you build. diff --git a/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx b/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx index f4936b6e14..c547e6e6ea 100644 --- a/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx +++ b/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx @@ -32,7 +32,7 @@ For nested collections I considered three common patterns: Postgres has had `ltree` since 2002. It stores dotted paths and exposes `@>` / `<@` for ancestor and descendant checks, `lquery` (Postgres's path pattern type) for subtree matches, and `lca` (lowest common ancestor) when you need the shared ancestor. It is also a trusted extension, so on a self-managed Postgres any role with `CREATE` can install it (managed hosts may still gate `CREATE EXTENSION`). -Hierarchies like this show up in category trees, file systems, org charts, and taxonomies. An org chart path like `company.engineering.platform` uses the same shape as `essays.drafts.chapter_1`, and [Prisma users have asked for native `ltree` support](https://github.com/prisma/prisma/issues/2568) since May 2020, alongside plenty of similar requests for other database features. +Hierarchies like this show up in category trees, file systems, org charts, and taxonomies. An org chart path like `company.engineering.platform` uses the same shape as `essays.drafts.chapter_1`, and [Prisma users have asked for native `ltree` support](https://github.com/prisma/orm/issues/2568) since May 2020, alongside plenty of similar requests for other database features. Once this project needed a real tree type, Prisma 8's extension system let me add `ltree` without waiting for it to land in core, exactly the gap the [call for extension authors](/prisma-next-call-for-extension-authors) invites the community to fill. I leaned on an agent while reading the Prisma 8 codebase; that made understanding the extension model, and then writing the pack, faster than digging through it by hand alone. diff --git a/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx b/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx index d5e7ebed07..aefc73a1b4 100644 --- a/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx +++ b/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx @@ -113,4 +113,4 @@ To add Prisma 8 to an existing app, run: bunx prisma@latest orm init ``` -To learn more, start with the [announcement blog post](https://pris.ly/pn-ea). Star and watch [prisma/prisma](https://github.com/prisma/prisma) on GitHub to follow what ships next, and if you hit a snag, start a thread in [`#prisma-next` on our Discord](https://pris.ly/discord). +To learn more, start with the [announcement blog post](https://pris.ly/pn-ea). Star and watch [prisma/prisma](https://github.com/prisma/orm) on GitHub to follow what ships next, and if you hit a snag, start a thread in [`#prisma-next` on our Discord](https://pris.ly/discord). diff --git a/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx b/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx index c22ce5d66d..f6a5f2545a 100644 --- a/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx +++ b/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx @@ -89,7 +89,7 @@ You can start building with Prisma 8 today. Run `npx prisma@latest orm init`, op The API is still settling, so expect breaking changes often. If you find rough edges or something you were hoping for that's missing, drop into [`#prisma-next` on Discord](https://pris.ly/discord) and tell us. Feedback right now is the most valuable thing we can get. -Star or watch [`prisma/prisma` on GitHub](https://github.com/prisma/prisma) to follow updates as they land, and subscribe to the [Prisma blog](https://www.prisma.io/blog) for the monthly milestone update. +Star or watch [`prisma/prisma` on GitHub](https://github.com/prisma/orm) to follow updates as they land, and subscribe to the [Prisma blog](https://www.prisma.io/blog) for the monthly milestone update. Prisma 8 is not yet production-ready. Prisma 7 remains the right choice for production today. diff --git a/apps/blog/content/blog/prisma-next-roadmap/index.mdx b/apps/blog/content/blog/prisma-next-roadmap/index.mdx index cf341c406a..9f65a8ae1f 100644 --- a/apps/blog/content/blog/prisma-next-roadmap/index.mdx +++ b/apps/blog/content/blog/prisma-next-roadmap/index.mdx @@ -69,6 +69,6 @@ For teams looking to upgrade, you'll be able to run Prisma 8 and Prisma 7 in par ## Follow along -For the most up-to-date view, follow the [roadmap in the Prisma 8 repo](https://github.com/prisma/prisma/blob/main/ROADMAP.md) as it develops in real time. We'll post announcements like this one as we learn more. +For the most up-to-date view, follow the [roadmap in the Prisma 8 repo](https://github.com/prisma/orm/blob/main/ROADMAP.md) as it develops in real time. We'll post announcements like this one as we learn more. -For the broader picture, [check out the Prisma 8 repo](https://github.com/prisma/prisma) and star it to subscribe to updates. +For the broader picture, [check out the Prisma 8 repo](https://github.com/prisma/orm) and star it to subscribe to updates. diff --git a/apps/blog/content/blog/prisma-orm-6-6-0-esm-support-d1-migrations-and-prisma-mcp-server/index.mdx b/apps/blog/content/blog/prisma-orm-6-6-0-esm-support-d1-migrations-and-prisma-mcp-server/index.mdx index 271686f643..59d4b30f56 100644 --- a/apps/blog/content/blog/prisma-orm-6-6-0-esm-support-d1-migrations-and-prisma-mcp-server/index.mdx +++ b/apps/blog/content/blog/prisma-orm-6-6-0-esm-support-d1-migrations-and-prisma-mcp-server/index.mdx @@ -13,11 +13,11 @@ tags: - "orm" --- -The [v6.6.0 Prisma ORM release](https://github.com/prisma/prisma/releases/tag/6.6.0) comes packed with exciting features: ESM support via a new generator, Early Access support for Cloudflare D1 and Turso migrations, an MCP server for managing databases directly in your favorite AI tools, and more. +The [v6.6.0 Prisma ORM release](https://github.com/prisma/orm/releases/tag/6.6.0) comes packed with exciting features: ESM support via a new generator, Early Access support for Cloudflare D1 and Turso migrations, an MCP server for managing databases directly in your favorite AI tools, and more. ## Prisma ORM v6.6.0 is out -Since publishing our [ORM manifesto](https://www.prisma.io/blog/prisma-orm-manifesto), we've been shipping meaningful improvements to Prisma ORM at a steady pace. In v6.6.0, we are bringing long-awaited features like [ESM support](https://github.com/prisma/prisma/issues/5030) and an initial version of pushing schemas changes to D1 and Turso databases to life. +Since publishing our [ORM manifesto](https://www.prisma.io/blog/prisma-orm-manifesto), we've been shipping meaningful improvements to Prisma ORM at a steady pace. In v6.6.0, we are bringing long-awaited features like [ESM support](https://github.com/prisma/orm/issues/5030) and an initial version of pushing schemas changes to D1 and Turso databases to life. ## ESM support with more flexible `prisma-client` generator (Early Access) @@ -57,7 +57,7 @@ As of now, we recommend keeping the generated `'./generated/prisma'` folder out ``` We see the `prisma-client` generator as the more modern version compared to `prisma-client-js` and will make it the default generator with the next major version increment in Prisma 7. Here are some more exciting features we're planning to add: -- splitting the generated generated Prisma Client file to avoid [slowing down code editors](https://github.com/prisma/prisma/issues/4807) due to long generated files +- splitting the generated generated Prisma Client file to avoid [slowing down code editors](https://github.com/prisma/orm/issues/4807) due to long generated files - no more need for the Accelerate extension when using Prisma Postgres ## MCP server to manage Prisma Postgres via LLMs (Preview) @@ -146,7 +146,7 @@ npx prisma init --vibe "Cat meme generator" ``` ## The future of Prisma ORM is exciting -This is just the beginning, we have a lot more exciting things coming to Prisma ORM in the next weeks and months — check out our [3-months roadmap](https://github.com/prisma/prisma/issues/26592) to get a glimpse of what's next or catch up on the most recent developments in our [changelog](https://www.prisma.io/changelog) (such as the [performance improvements gained from our move from Rust to TypeScript](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance)). +This is just the beginning, we have a lot more exciting things coming to Prisma ORM in the next weeks and months — check out our [3-months roadmap](https://github.com/prisma/orm/issues/26592) to get a glimpse of what's next or catch up on the most recent developments in our [changelog](https://www.prisma.io/changelog) (such as the [performance improvements gained from our move from Rust to TypeScript](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance)). If you want to try the new workflows from this release, explore [Prisma ORM](https://www.prisma.io/orm), configure [Prisma's MCP tooling](https://www.prisma.io/mcp), or spin up [Prisma Postgres](https://www.prisma.io/postgres) for the database side of the experience. diff --git a/apps/blog/content/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview/index.mdx b/apps/blog/content/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview/index.mdx index 3336d1e2dd..0bb2912e86 100644 --- a/apps/blog/content/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview/index.mdx +++ b/apps/blog/content/blog/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview/index.mdx @@ -28,7 +28,7 @@ Prisma ORM supports two strategies for loading related data. With the `join` str ## The two join strategies in Prisma ORM -[Support for database-level joins](https://github.com/prisma/prisma/issues/5184) was one of the most requested features in Prisma ORM, and it shipped as the `relationLoadStrategy` option. +[Support for database-level joins](https://github.com/prisma/orm/issues/5184) was one of the most requested features in Prisma ORM, and it shipped as the `relationLoadStrategy` option. ![](/prisma-orm-now-lets-you-choose-the-best-join-strategy-preview/imgs/7273f2beaf20bbf771e47bb7b542b3c21c31e19c-800x653.svg) For any relation query with `include` (or `select`), the top-level `relationLoadStrategy` option accepts one of two values: @@ -361,4 +361,4 @@ Like Prisma ORM, Prisma 8 pairs with [Prisma Postgres](https://www.prisma.io/pos ## Try it out and share your feedback -We'd love for you to try out the `join` relation load strategy. If you don't have a database at hand, `npm create db` gives you a free Prisma Postgres database to experiment with. Let us know what you think and [share your feedback with us](https://github.com/prisma/prisma/discussions/22288)! +We'd love for you to try out the `join` relation load strategy. If you don't have a database at hand, `npm create db` gives you a free Prisma Postgres database to experiment with. Let us know what you think and [share your feedback with us](https://github.com/prisma/orm/discussions/22288)! diff --git a/apps/blog/content/blog/prisma-orm-support-for-edge-functions-is-now-in-preview/index.mdx b/apps/blog/content/blog/prisma-orm-support-for-edge-functions-is-now-in-preview/index.mdx index f2ed4a6bdb..5afd1b91ce 100644 --- a/apps/blog/content/blog/prisma-orm-support-for-edge-functions-is-now-in-preview/index.mdx +++ b/apps/blog/content/blog/prisma-orm-support-for-edge-functions-is-now-in-preview/index.mdx @@ -50,7 +50,7 @@ It was not possible to "just" deploy an app with Prisma ORM to the edge due to t ![](/prisma-orm-support-for-edge-functions-is-now-in-preview/imgs/b67a096af36af4026cd5c6b36b34a7693d0f2ce1-2532x1210.png) -We are excited that the [`v5.11.0`](https://github.com/prisma/prisma/releases/tag/5.11.0) release lifts these restrictions and enables running Prisma ORM in edge functions in Preview 🎉 +We are excited that the [`v5.11.0`](https://github.com/prisma/orm/releases/tag/5.11.0) release lifts these restrictions and enables running Prisma ORM in edge functions in Preview 🎉 ![](/prisma-orm-support-for-edge-functions-is-now-in-preview/imgs/4a84546e5ae706f5a2a15e67a4757260d14b1273-2532x1210.png) @@ -236,4 +236,4 @@ This command will deploy your edge function to Cloudflare and output the URL whe We would love to know what you think! Try out the new support for edge deployments using [Vercel](https://www.prisma.io/docs/orm/v7/prisma-client/deployment/edge/deploy-to-vercel) or [Cloudflare](https://www.prisma.io/docs/orm/v7/prisma-client/deployment/edge/deploy-to-cloudflare) and share your feedback with us via [X](https://pris.ly/x) or [Discord](http://pris.ly/discord) 🚀 -If you run into any issues, you can create a bug report [here](https://github.com/prisma/prisma/issues/new/choose). +If you run into any issues, you can create a bug report [here](https://github.com/prisma/orm/issues/new/choose). diff --git a/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx b/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx index 6697909b9c..93d28d283c 100644 --- a/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx +++ b/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx @@ -163,7 +163,7 @@ if (cluster.isPrimary) { ## Keeping things moving -We are continuing to improve Prisma 7 performance and want to hear from you if you are still experiencing performance issues after applying the recommendations above. Please open an issue on [GitHub](https://github.com/prisma/prisma/issues) with details about your setup and the performance characteristics you are seeing. +We are continuing to improve Prisma 7 performance and want to hear from you if you are still experiencing performance issues after applying the recommendations above. Please open an issue on [GitHub](https://github.com/prisma/orm/issues) with details about your setup and the performance characteristics you are seeing. Be sure to follow us on social media to stay up to date with the latest releases of Prisma ORM and Prisma Postgres: diff --git a/apps/blog/content/blog/prisma-orm-without-rust-latest-performance-benchmarks/index.mdx b/apps/blog/content/blog/prisma-orm-without-rust-latest-performance-benchmarks/index.mdx index 31e86ca16b..e859b9272e 100644 --- a/apps/blog/content/blog/prisma-orm-without-rust-latest-performance-benchmarks/index.mdx +++ b/apps/blog/content/blog/prisma-orm-without-rust-latest-performance-benchmarks/index.mdx @@ -24,7 +24,7 @@ Our move from Rust to TypeScript in the Prisma ORM internals is now in Preview f ### TL;DR: The Rust-Free ORM is ready for production-use -Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/prisma/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. +Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/orm/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. - **No binary overhead:** The dependency on native Rust binaries is eliminated, drastically simplifying deployment and reducing potential complexity issues. - **Performance:** Get **up to 3.4x faster queries** (by removing cross-language serialization) and a **90% smaller bundle size** (from ~14MB to 1.6 MB). @@ -36,7 +36,7 @@ To implement these benefits now, see the [official usage guide for the new Rust- Our move from Rust to TypeScript not only improves the developer experience, it also makes Prisma ORM more flexible and easier to use—whether you're working with different JavaScript runtimes, deployment platforms, or project setups like monorepos. On top of that, it brings significant performance improvements. -Over the past few [releases](https://github.com/prisma/prisma/releases/), we’ve gradually rolled out [Preview](https://www.prisma.io/docs/orm/v7/more/releases#preview) support for Prisma ORM for all major SQL databases supported by Prisma ORM. It’s now available for: PostgreSQL, CockroachDB, Neon, MySQL, MariaDB, PlanetScale, SQLite, D1 and MS SQL Server databases. +Over the past few [releases](https://github.com/prisma/orm/releases/), we’ve gradually rolled out [Preview](https://www.prisma.io/docs/orm/v7/more/releases#preview) support for Prisma ORM for all major SQL databases supported by Prisma ORM. It’s now available for: PostgreSQL, CockroachDB, Neon, MySQL, MariaDB, PlanetScale, SQLite, D1 and MS SQL Server databases. Our work on moving away from Rust continues with the goal of making “Rust-free” Prisma ORM the default in the upcoming Prisma v7 release. In this article, we are sharing an update on the performance improvements we’ve measured using the latest Rust-free Preview version of Prisma ORM. diff --git a/apps/blog/content/blog/prisma-preview-cockroach-db-release/index.mdx b/apps/blog/content/blog/prisma-preview-cockroach-db-release/index.mdx index 16ae92c4a7..4727b2d157 100644 --- a/apps/blog/content/blog/prisma-preview-cockroach-db-release/index.mdx +++ b/apps/blog/content/blog/prisma-preview-cockroach-db-release/index.mdx @@ -30,7 +30,7 @@ Today we are excited to expand the range of Prisma compatible databases with Pre ## CockroachDB support in Prisma is now in Preview -Today we are excited to introduce Preview support for [CockroachDB](https://www.cockroachlabs.com/product/) as part of the [3.9.0 release](https://github.com/prisma/prisma/releases/tag/3.9.0) of Prisma! 🎉 +Today we are excited to introduce Preview support for [CockroachDB](https://www.cockroachlabs.com/product/) as part of the [3.9.0 release](https://github.com/prisma/orm/releases/tag/3.9.0) of Prisma! 🎉 CockroachDB is a distributed SQL database that shines in its ability to scale efficiently while maintaining developer agility and reducing operational overhead. @@ -40,13 +40,13 @@ CockroachDB support in Prisma is the product of collaboration with the [Cockroac **However, as a [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) feature, it is not production-ready and comes with some limitations.** To learn more about the current limitations, see the [limitations section](#limitations). -Today, we're inviting the CockroachDB community to [**try it out**](https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-cockroachdb) and [**give us feedback**](https://github.com/prisma/prisma/issues/11542), so we can bring CockroachDB support to General Availability. +Today, we're inviting the CockroachDB community to [**try it out**](https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-cockroachdb) and [**give us feedback**](https://github.com/prisma/orm/issues/11542), so we can bring CockroachDB support to General Availability. Your feedback and suggestions will help us shape the future of CockroachDB support in Prisma. 🙌 ## Prisma - making databases easy -Prisma is a [next-generation](https://www.prisma.io/docs/concepts/overview/prisma-in-your-stack/is-prisma-an-orm) [open-source](https://www.github.com/prisma/prisma) ORM for Node.js and TypeScript. It helps you be more productive and confident when developing database-driven applications. +Prisma is a [next-generation](https://www.prisma.io/docs/concepts/overview/prisma-in-your-stack/is-prisma-an-orm) [open-source](https://www.github.com/prisma/orm) ORM for Node.js and TypeScript. It helps you be more productive and confident when developing database-driven applications. It can be used as an alternative to traditional ORMs and SQL query builders to interact with your database. @@ -107,7 +107,7 @@ You can also dig into our ready-to-run [example](https://github.com/prisma/prism ## Limitations -Prisma Migrate is not supported yet with CockroachDB; if you're starting without an existing database, you will need to define the schema with SQL. To follow progress on this, subscribe to the [related issue](https://github.com/prisma/prisma/issues/4702). +Prisma Migrate is not supported yet with CockroachDB; if you're starting without an existing database, you will need to define the schema with SQL. To follow progress on this, subscribe to the [related issue](https://github.com/prisma/orm/issues/4702). We are working on adding support for CockroachDB in Prisma Migrate, which will be available soon; and fully supported when the CockroachDB connector is Generally Available. @@ -118,9 +118,9 @@ CockroachDB supports the PostgreSQL wire protocol and the majority of PostgreSQL ## Try Prisma with your existing CockroachDB database and share your feedback -We built this for you and are eager to [hear your feedback](https://github.com/prisma/prisma/issues/11542)! +We built this for you and are eager to [hear your feedback](https://github.com/prisma/orm/issues/11542)! -🐜 Found something you'd love to see improved? Please [file an issue](https://github.com/prisma/prisma/issues/new/choose) so our engineering team can look into it. +🐜 Found something you'd love to see improved? Please [file an issue](https://github.com/prisma/orm/issues/new/choose) so our engineering team can look into it.
[Get started with Prisma and CockroachDB](https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-cockroachdb) diff --git a/apps/blog/content/blog/prisma-raises-series-a-saks1zr7kip6/index.mdx b/apps/blog/content/blog/prisma-raises-series-a-saks1zr7kip6/index.mdx index 1f40dc167e..371d859bd0 100644 --- a/apps/blog/content/blog/prisma-raises-series-a-saks1zr7kip6/index.mdx +++ b/apps/blog/content/blog/prisma-raises-series-a-saks1zr7kip6/index.mdx @@ -95,7 +95,7 @@ After running Preview and Beta versions for more than a year, we've recently [la Prisma's main feature is [Prisma Client](https://www.prisma.io/docs/concepts/components/prisma-client), an auto-generated and type-safe query builder which can be used to access a database in Node.js and TypeScript. Thanks to [introspection](https://www.prisma.io/docs/concepts/components/introspection), Prisma Client can be used to work with any existing database! -> **Note**: Prisma currently supports **PostgreSQL**, **MySQL** and **SQLite** databases – with more planned. Please create [new GitHub issues](https://github.com/prisma/prisma/issues/new) or subscribe to existing ones (e.g. for [MongoDB](https://github.com/prisma/prisma/issues?q=is%3Aissue+is%3Aopen+mongo) or [DynamoDB](https://github.com/prisma/prisma/issues/1676)) if you'd like to see support for specific databases. +> **Note**: Prisma currently supports **PostgreSQL**, **MySQL** and **SQLite** databases – with more planned. Please create [new GitHub issues](https://github.com/prisma/orm/issues/new) or subscribe to existing ones (e.g. for [MongoDB](https://github.com/prisma/orm/issues?q=is%3Aissue+is%3Aopen+mongo) or [DynamoDB](https://github.com/prisma/orm/issues/1676)) if you'd like to see support for specific databases. ### Next-generation web frameworks are built on Prisma @@ -151,7 +151,7 @@ This architecture enables us to expand Prisma Client to other languages and brin Prisma is designed in a way that it can potentially connect to _any_ existing data source as long as there is the right _connector_ for it! -As of today, we've built connectors for PostgreSQL, MySQL and SQLite. A [connector for MongoDB](https://github.com/prisma/prisma/issues/1277) is already in the works and more are planned for the future. +As of today, we've built connectors for PostgreSQL, MySQL and SQLite. A [connector for MongoDB](https://github.com/prisma/orm/issues/1277) is already in the works and more are planned for the future. ![Prisma supporting a broad spectrum of databases and other data sources](/prisma-raises-series-a-saks1zr7kip6/imgs/PQSljF7.png) @@ -165,7 +165,7 @@ We are committed to building world-class open-source tools to solve common datab ## We 💚 our community -We are incredibly grateful for everyone who has accompanied us on our journey! It is fantastic to see our lively community on [Slack](https://slack.prisma.io), [GitHub](https://github.com/prisma/prisma), [Twitter](https://pris.ly/x) and a lot of other channels where folks are chatting about Prisma and helping each other out! +We are incredibly grateful for everyone who has accompanied us on our journey! It is fantastic to see our lively community on [Slack](https://slack.prisma.io), [GitHub](https://github.com/prisma/orm), [Twitter](https://pris.ly/x) and a lot of other channels where folks are chatting about Prisma and helping each other out! diff --git a/apps/blog/content/blog/prisma-sql-server-support-preview-a4anl2gd8d3a/index.mdx b/apps/blog/content/blog/prisma-sql-server-support-preview-a4anl2gd8d3a/index.mdx index d3c107db6e..468c7a9ac4 100644 --- a/apps/blog/content/blog/prisma-sql-server-support-preview-a4anl2gd8d3a/index.mdx +++ b/apps/blog/content/blog/prisma-sql-server-support-preview-a4anl2gd8d3a/index.mdx @@ -23,7 +23,7 @@ Today we are excited to expand the range of supported database providers with pr ## TL;DR -- Prisma release [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) adds preview support for Microsoft SQL Server. +- Prisma release [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) adds preview support for Microsoft SQL Server. - You can use Prisma Client with SQL Server through introspection. - Check out the [**Start from scratch guide**](https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-sqlserver) in the docs. @@ -33,12 +33,12 @@ Today we are excited to introduce an initial preview of support for SQL Server! Earlier this year we released Prisma Client for general availability with support for PostgreSQL, MySQL, SQLite, and MariaDB. Since then, we've heard from thousands of engineers about how Prisma Client is helping them build apps faster by making database access easy. -This release marks the first milestone since [SQL Server was originally requested](https://github.com/prisma/prisma/issues/2430) by a community member. We are now a step closer to providing the same streamlined developer experience, type safety, and productivity to developers using SQL Server +This release marks the first milestone since [SQL Server was originally requested](https://github.com/prisma/orm/issues/2430) by a community member. We are now a step closer to providing the same streamlined developer experience, type safety, and productivity to developers using SQL Server SQL Server support has passed rigorous testing internally, and is now ready for testing by the community, **however, as a preview feature, it is not production-ready.** To read more about what preview means, check out the [maturity levels](https://www.prisma.io/docs/about/prisma/releases#preview) in the Prisma docs. -Thus, we're inviting the SQL Server community to try it out and [give us feedback](https://github.com/prisma/prisma/issues/4039) so we can bring SQL Server support to general availability. 🚀 +Thus, we're inviting the SQL Server community to try it out and [give us feedback](https://github.com/prisma/orm/issues/4039) so we can bring SQL Server support to general availability. 🚀 Your feedback and suggestion will help us shape the future of SQL Server support in Prisma. 🙌 @@ -62,7 +62,7 @@ Support for SQL Server comes with some limitations that are detailed in this sec Prisma Migrate does not support SQL Server yet. This means that you can continue using whichever migration tool to alter the database schema and then use introspection to keep the Prisma schema in sync with the database schema. -To follow progress on this issue, subscribe to [issue #4074 on GitHub](https://github.com/prisma/prisma/issues/4074). +To follow progress on this issue, subscribe to [issue #4074 on GitHub](https://github.com/prisma/orm/issues/4074). **TLS encryption should be disabled when connecting from macOS** @@ -72,7 +72,7 @@ To disable encryption, add the `encrypt=DANGER_PLAINTEXT` parameter to the conne > **Note that disabling TLS should only be done during development as it's a security risk otherwise.** -To follow progress on this issue, subscribe to [issue #4075 on GitHub](https://github.com/prisma/prisma/issues/4075) +To follow progress on this issue, subscribe to [issue #4075 on GitHub](https://github.com/prisma/orm/issues/4075) **TCP required on the service** @@ -86,7 +86,7 @@ We built this for you and are eager to hear your feedback! ☎️ [Schedule a call](https://calendly.com/labas-prisma/sqlserver-feedback) with our Product team to tell us everything about your project, and get an exclusive T-Shirt. -🐜 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/prisma/issues/new/choose) so we can look into it. +🐜 Tried it out and found that it's missing something or stumbled upon a bug? Please [file an issue](https://github.com/prisma/orm/issues/new/choose) so we can look into it. 🌍 We also invite you to join our [Slack](https://slack.prisma.io/) where you can discuss all things Prisma, share feedback in the `#product-feedback` channel, and get help from the community. diff --git a/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx b/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx index 5043c740c0..4bca76a358 100644 --- a/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx +++ b/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx @@ -242,7 +242,7 @@ npm create prisma@latest Model something, apply two migrations, and open **Migrations**. Tell us what you'd want in the timeline next on [Discord](https://pris.ly/discord). -**Star and watch [prisma/prisma](https://github.com/prisma/prisma) on GitHub** to follow development. +**Star and watch [prisma/prisma](https://github.com/prisma/orm) on GitHub** to follow development. --- diff --git a/apps/blog/content/blog/prisma-the-complete-orm-inw24qjeawmb/index.mdx b/apps/blog/content/blog/prisma-the-complete-orm-inw24qjeawmb/index.mdx index 94c6a20f44..00fe6d47d4 100644 --- a/apps/blog/content/blog/prisma-the-complete-orm-inw24qjeawmb/index.mdx +++ b/apps/blog/content/blog/prisma-the-complete-orm-inw24qjeawmb/index.mdx @@ -29,7 +29,7 @@ Prisma is a next-generation ORM for Node.js and TypeScript. After more than two ## A new paradigm for object-relational mapping -Prisma is a next-generation and [open-source](https://www.github.com/prisma/prisma) ORM for Node.js and TypeScript. It consists of the following tools: +Prisma is a next-generation and [open-source](https://www.github.com/prisma/orm) ORM for Node.js and TypeScript. It consists of the following tools: - [**Prisma Client**](https://www.prisma.io/client): Auto-generated and type-safe database client - [**Prisma Migrate**](https://www.prisma.io/migrate): Declarative data modeling and customizable migrations @@ -292,11 +292,11 @@ Used by thousands of companies since the initial release three years ago, Prisma ### We care about developers -Prisma is developed in the [open](https://github.com/prisma/prisma). Our Product and Engineering teams are monitoring GitHub issues and typically respond within 24 hours after an issue is opened. +Prisma is developed in the [open](https://github.com/prisma/orm). Our Product and Engineering teams are monitoring GitHub issues and typically respond within 24 hours after an issue is opened. -New [releases](https://github.com/prisma/prisma/releases) happen every two weeks with new features, bug fixes and lots of improvements. After each release, we do a [livestream on Youtube](https://www.youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) to present the new features and get feedback from our community. +New [releases](https://github.com/prisma/orm/releases) happen every two weeks with new features, bug fixes and lots of improvements. After each release, we do a [livestream on Youtube](https://www.youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) to present the new features and get feedback from our community. -We also try to help developers wherever they raise questions about Prisma, be it on [Slack](https://slack.prisma.io), [GitHub Discussions](https://github.com/prisma/prisma/discussions) or [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) via a dedicated Community Support team. +We also try to help developers wherever they raise questions about Prisma, be it on [Slack](https://slack.prisma.io), [GitHub Discussions](https://github.com/prisma/orm/discussions) or [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) via a dedicated Community Support team. Here is our community in numbers: @@ -306,7 +306,7 @@ Here is our community in numbers: | Resolved support requests (GitHub, Slack, Stackoverflow, ...) | **> 3k** | | Members on Prisma Slack | **> 40k** | | GitHub contributors across repos | **> 300** | -| GitHub stars ([help us get to 10k](https://github.com/prisma/prisma) 🌟) | **> 9,9k** | +| GitHub stars ([help us get to 10k](https://github.com/prisma/orm) 🌟) | **> 9,9k** | | Shipped sticker packs in 2021 (order your stickers [here](https://gist.github.com/nikolasburk/5b64014d41bc21594808cea82621df83)) | **> 100** | | Hosted developer events since 2017 (Meetups, conferences, ...) | **> 50** | @@ -430,7 +430,7 @@ There are various ways to get started with Prisma: ## Come for the ORM, stay for the community 💚 -[Community](https://www.prisma.io/community) has been incredibly important for us since we've started. From hosting Meetups and conferences to helping out users on [Slack](https://slack.prisma.io) and [GitHub Discussions](https://github.com/prisma/prisma/discussions) we are always trying to be closely in touch with the developer community. Come join us! +[Community](https://www.prisma.io/community) has been incredibly important for us since we've started. From hosting Meetups and conferences to helping out users on [Slack](https://slack.prisma.io) and [GitHub Discussions](https://github.com/prisma/orm/discussions) we are always trying to be closely in touch with the developer community. Come join us! diff --git a/apps/blog/content/blog/prisma-turso-ea-support-rXGd_Tmy3UXX/index.mdx b/apps/blog/content/blog/prisma-turso-ea-support-rXGd_Tmy3UXX/index.mdx index 0933521476..27af6b4866 100644 --- a/apps/blog/content/blog/prisma-turso-ea-support-rXGd_Tmy3UXX/index.mdx +++ b/apps/blog/content/blog/prisma-turso-ea-support-rXGd_Tmy3UXX/index.mdx @@ -189,7 +189,7 @@ If you cloned the `typescript/script` example, you can run `npm run dev` to inse The setup above uses a **single** remote database. You can take it a step further by [setting up database replicas](https://docs.turso.tech/tutorials/get-started-turso-cli/step-05-replicate-database-another-location#replicate-a-database-by-adding-a-location-to-its-placement-group). Turso automatically picks the closest replica to your app for read queries when you create replicas. No additional logic is required to define how the routing of the read queries should be handled. Write queries will be forwarded to the primary database. -Try it out and share your feedback! We encourage you to [create an issue](https://github.com/prisma/prisma/issues/new/choose) if you find something missing or run into a bug. +Try it out and share your feedback! We encourage you to [create an issue](https://github.com/prisma/orm/issues/new/choose) if you find something missing or run into a bug. --- @@ -273,7 +273,7 @@ It will be interesting to see what other use cases you will come up with for thi ## Try it out yourself! -We can't wait to see what you build with Turso and Prisma. We encourage you to try it out and [let us know your thoughts](https://github.com/prisma/prisma/discussions/21345). +We can't wait to see what you build with Turso and Prisma. We encourage you to try it out and [let us know your thoughts](https://github.com/prisma/orm/discussions/21345). We’re also working on supporting other serverless database drivers and edge function deployments. Take [this short survey](https://pris.ly/survey/driver-adapters-turso-blog) and leave us your email address for updates. diff --git a/apps/blog/content/blog/read-replicas-prisma-client-extension-f66prwk56wow/index.mdx b/apps/blog/content/blog/read-replicas-prisma-client-extension-f66prwk56wow/index.mdx index c8a4ea3fa0..9520bf4f4c 100644 --- a/apps/blog/content/blog/read-replicas-prisma-client-extension-f66prwk56wow/index.mdx +++ b/apps/blog/content/blog/read-replicas-prisma-client-extension-f66prwk56wow/index.mdx @@ -55,7 +55,7 @@ There are multiple ways to integrate read replicas in an application. One way yo Another way to integrate read replicas in your app is via the _data layer_, for example the database driver, query builder or Object Relational Mapper (ORM). In this case, you could provide multiple connection strings to your data layer, your primary instance and replicas. The data layer then orchestrates request distribution by directing queries to a suitable replica. -In the Node.js ecosystem, Prisma is one of the most popular libraries for implementing the application data layer. [Support for read replicas](https://github.com/prisma/prisma/issues/172) in Prisma Client is one of the most requested features. +In the Node.js ecosystem, Prisma is one of the most popular libraries for implementing the application data layer. [Support for read replicas](https://github.com/prisma/orm/issues/172) in Prisma Client is one of the most requested features. We're excited to share the [`@prisma/extension-read-replicas`](https://pris.ly/read-replica-extension) extension, which achieves this with a Prisma Client extension! @@ -184,7 +184,7 @@ A significant advantage of having the extension as a separate package rather tha A side-effect of shipping it as a separate package/repository is that the codebase will remain relatively small and manageable. This will allow our community members to contribute by creating pull requests to improve the extension. -While [Prisma Client extensions](https://www.prisma.io/docs/orm/v7/prisma-client/client-extensions) have been Generally Available since Prisma [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0), we also used the experience from building an extension ourselves as an opportunity to make further improvements to the Prisma Client extension API. For example, in [5.2.0](https://github.com/prisma/prisma/releases/tag/5.2.0), as preparation for this extension, we removed the datasource name in Prisma Client's constructor configuration, to simplify programmatic connection string overrides, which the extension uses. We also created a few more GitHub issues for [future improvements to Client Extensions](https://github.com/prisma/prisma/issues?q=is:open+label:%22topic:+clientExtensions%22+label:kind/improvement+sort:updated-desc+). Please leave an upvote or comment if you're interested in any of these improvements. +While [Prisma Client extensions](https://www.prisma.io/docs/orm/v7/prisma-client/client-extensions) have been Generally Available since Prisma [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0), we also used the experience from building an extension ourselves as an opportunity to make further improvements to the Prisma Client extension API. For example, in [5.2.0](https://github.com/prisma/orm/releases/tag/5.2.0), as preparation for this extension, we removed the datasource name in Prisma Client's constructor configuration, to simplify programmatic connection string overrides, which the extension uses. We also created a few more GitHub issues for [future improvements to Client Extensions](https://github.com/prisma/orm/issues?q=is:open+label:%22topic:+clientExtensions%22+label:kind/improvement+sort:updated-desc+). Please leave an upvote or comment if you're interested in any of these improvements. ## Try it out yourself diff --git a/apps/blog/content/blog/rust-to-typescript-update-boosting-prisma-orm-performance/index.mdx b/apps/blog/content/blog/rust-to-typescript-update-boosting-prisma-orm-performance/index.mdx index 1f76f847c2..80829dc094 100644 --- a/apps/blog/content/blog/rust-to-typescript-update-boosting-prisma-orm-performance/index.mdx +++ b/apps/blog/content/blog/rust-to-typescript-update-boosting-prisma-orm-performance/index.mdx @@ -21,7 +21,7 @@ The Query Compiler project upgrades Prisma ORM by swapping out the traditional R ### TL;DR: The Rust-Free ORM is ready for production-use -Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/prisma/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. +Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/orm/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. - **No binary overhead:** The dependency on native Rust binaries is eliminated, drastically simplifying deployment and reducing potential complexity issues. - **Performance:** Get **up to 3.4x faster queries** (by removing cross-language serialization) and a **90% smaller bundle size** (from ~14MB to 1.6 MB). @@ -91,7 +91,7 @@ We’re very excited about what this means for Prisma ORM users. The breakthroug As always, our focus in on our community and we’d love to hear your thoughts! -- Keep up with the latest updates and [join the conversation on GitHub](https://github.com/prisma/prisma/discussions) +- Keep up with the latest updates and [join the conversation on GitHub](https://github.com/prisma/orm/discussions) - [Ask us burning questions on Discord](https://pris.ly/discord) in our dev AMAs - Even [run the benchmarks](https://pris.ly/qc-benchmark-repo) yourself! diff --git a/apps/blog/content/blog/series-b-announcement-v8t12ksi6x/index.mdx b/apps/blog/content/blog/series-b-announcement-v8t12ksi6x/index.mdx index ebebcc5885..385f64ed10 100644 --- a/apps/blog/content/blog/series-b-announcement-v8t12ksi6x/index.mdx +++ b/apps/blog/content/blog/series-b-announcement-v8t12ksi6x/index.mdx @@ -236,9 +236,9 @@ Needless to say that we are hiring for several roles across the entire organizat We will continue to invest into the open-source ORM as the foundation for our commercial offering! Check out our [roadmap](https://pris.ly/roadmap) to learn about the exciting features we are going to build. -The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). +The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). -You can also start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. If you never want to miss any news from the Prisma community, [follow us on X/Twitter](https://pris.ly/x). diff --git a/apps/blog/content/blog/serverless-database-drivers-KML1ehXORxZV/index.mdx b/apps/blog/content/blog/serverless-database-drivers-KML1ehXORxZV/index.mdx index 5debf9c8c8..2be6041c53 100644 --- a/apps/blog/content/blog/serverless-database-drivers-KML1ehXORxZV/index.mdx +++ b/apps/blog/content/blog/serverless-database-drivers-KML1ehXORxZV/index.mdx @@ -137,7 +137,7 @@ const prisma = new PrismaClient({ adapter }); // Use Prisma Client as normal ``` -Now your code has built-in benefits of the Neon serverless driver, such as WebSocket connections and [message pipelining](https://neon.tech/blog/quicker-serverless-postgres), while Prisma covers connection creation and destruction, error handling, and type safety. If you have any feedback about our Neon Serverless Driver support, please leave a comment on our [dedicated GitHub issue](https://github.com/prisma/prisma/discussions/21346) and we'll use it as we continue development. +Now your code has built-in benefits of the Neon serverless driver, such as WebSocket connections and [message pipelining](https://neon.tech/blog/quicker-serverless-postgres), while Prisma covers connection creation and destruction, error handling, and type safety. If you have any feedback about our Neon Serverless Driver support, please leave a comment on our [dedicated GitHub issue](https://github.com/prisma/orm/discussions/21346) and we'll use it as we continue development. ### Use PlanetScale with `@planetscale/database` @@ -195,7 +195,7 @@ const prisma = new PrismaClient({ adapter }); // Use Prisma Client as normal ``` -Your Prisma Client instance now uses PlanetScale's [`database-js`](https://github.com/planetscale/database-js) which can [improve connection reliability and performance](https://planetscale.com/blog/faster-mysql-with-http3). It uses HTTP requests instead of Prisma’s connection pool, but Prisma will continue to handle error handling and type safety. If you have any feedback about our PlanetScale Serverless Driver support, please leave a comment on our [dedicated GitHub issue](https://github.com/prisma/prisma/discussions/21347) and we'll use it as we continue development. +Your Prisma Client instance now uses PlanetScale's [`database-js`](https://github.com/planetscale/database-js) which can [improve connection reliability and performance](https://planetscale.com/blog/faster-mysql-with-http3). It uses HTTP requests instead of Prisma’s connection pool, but Prisma will continue to handle error handling and type safety. If you have any feedback about our PlanetScale Serverless Driver support, please leave a comment on our [dedicated GitHub issue](https://github.com/prisma/orm/discussions/21347) and we'll use it as we continue development.
@@ -208,4 +208,4 @@ We're excited that Prisma users can now take advantage of the Neon and PlanetSca Prisma Client and the new driver adapters feature currently do not support Edge Functions deployments such as CloudFlare Workers or Vercel Edge Functions yet. If you want to test the Neon or PlanetScale Serverless Driver in Edge Functions environments, make sure to submit a [response to our survey](https://pris.ly/survey/driver-adapters-serverless-blog) so that you will be considered for Early Access to our edge function support as well. We'll have news soon. -We would love to know what you think! Try out the `driverAdapters` [Preview feature](https://www.prisma.io/docs/about/prisma/releases#preview) and pass any feedback you have via our GitHub disccussions for [Neon](https://github.com/prisma/prisma/discussions/21346) and [PlanetScale](https://github.com/prisma/prisma/discussions/21347) or on our [Discord](https://pris.ly/discord/driver-adapters). +We would love to know what you think! Try out the `driverAdapters` [Preview feature](https://www.prisma.io/docs/about/prisma/releases#preview) and pass any feedback you have via our GitHub disccussions for [Neon](https://github.com/prisma/orm/discussions/21346) and [PlanetScale](https://github.com/prisma/orm/discussions/21347) or on our [Discord](https://pris.ly/discord/driver-adapters). diff --git a/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx b/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx index 4124c8bd6b..ad60b55460 100644 --- a/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx +++ b/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx @@ -322,4 +322,4 @@ npx prisma@latest orm init Write a contract, plan a migration, and read the `migration.ts` and `ops.json` it produces. Then, from a feature branch, deploy to [Compute](https://www.prisma.io/docs/prisma-compute/deploy) with `npx @prisma/cli@latest app deploy --db`. The CLI targets your current Git branch, so that one command gives the branch its own database, ready for the expand-and-contract cycle. -Tell us what worked and what didn't on [Discord](https://pris.ly/discord) in the `#prisma-next` channel, and **star [prisma/prisma](https://github.com/prisma/prisma) on GitHub** to follow development. +Tell us what worked and what didn't on [Discord](https://pris.ly/discord) in the `#prisma-next` channel, and **star [prisma/prisma](https://github.com/prisma/orm) on GitHub** to follow development. diff --git a/apps/blog/content/blog/stop-your-ai-agent-dropping-your-database/index.mdx b/apps/blog/content/blog/stop-your-ai-agent-dropping-your-database/index.mdx index 133db53049..193354fc5e 100644 --- a/apps/blog/content/blog/stop-your-ai-agent-dropping-your-database/index.mdx +++ b/apps/blog/content/blog/stop-your-ai-agent-dropping-your-database/index.mdx @@ -50,7 +50,7 @@ Use the --accept-data-loss flag to ignore the data loss warnings An agent's goal is a green exit code, so it does what the error says. That's [how one schema-field request became 87 dropped tables](https://github.com/anthropics/claude-code/issues/36183): the `.env` pointed at production, and nothing in the tool knew or checked. -For years, classic Prisma's answer to migration drift was a prompt: *"We need to reset the database… All data will be lost."* One `y` away from disaster. We've since hardened what a human-era CLI can harden. Prisma 6.5 [stopped offering resets](https://github.com/prisma/prisma/issues/21483), and 6.15 [refuses the most destructive commands from detected agents](https://github.com/prisma/prisma/releases/tag/6.15.0) until a human explicitly consents. Other tools in the ecosystem have their own equivalents, with their own sync modes and force flags. +For years, classic Prisma's answer to migration drift was a prompt: *"We need to reset the database… All data will be lost."* One `y` away from disaster. We've since hardened what a human-era CLI can harden. Prisma 6.5 [stopped offering resets](https://github.com/prisma/orm/issues/21483), and 6.15 [refuses the most destructive commands from detected agents](https://github.com/prisma/orm/releases/tag/6.15.0) until a human explicitly consents. Other tools in the ecosystem have their own equivalents, with their own sync modes and force flags. But this isn't enough. The fix isn't a better warning. It's a system where the catastrophic action can't be initiated at all. @@ -183,4 +183,4 @@ npx prisma@latest orm init Then ask your agent to make a schema change and watch the workflow it follows: edit the contract, plan a migration, run it. That workflow, not a warning, is what stands between your agent and a viral screenshot. -[Star and watch the repo](https://github.com/prisma/prisma) to follow progress, and tell us what your agent gets wrong in the [Prisma Discord](https://pris.ly/discord). We're building this in the open, and agent-safety reports are exactly the feedback we're after. +[Star and watch the repo](https://github.com/prisma/orm) to follow progress, and tell us what your agent gets wrong in the [Prisma Discord](https://pris.ly/discord). We're building this in the open, and agent-safety reports are exactly the feedback we're after. diff --git a/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx b/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx index c31fd4d23e..bfea963445 100644 --- a/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx +++ b/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx @@ -270,7 +270,7 @@ const posts = await db.posts.forUser(userId).newestFirst().take(20).all(); ## Aggregation & grouping -If you missed support for `GROUP BY` ([like the people here](https://github.com/prisma/prisma/issues/8744)) in Prisma ORM, we have good news for you: +If you missed support for `GROUP BY` ([like the people here](https://github.com/prisma/orm/issues/8744)) in Prisma ORM, we have good news for you: ```ts title="aggregation.ts" const users = await db.users diff --git a/apps/blog/content/blog/top-5-myths-about-prisma-orm/index.mdx b/apps/blog/content/blog/top-5-myths-about-prisma-orm/index.mdx index 32fb57f7f4..2dfa64524e 100644 --- a/apps/blog/content/blog/top-5-myths-about-prisma-orm/index.mdx +++ b/apps/blog/content/blog/top-5-myths-about-prisma-orm/index.mdx @@ -33,7 +33,7 @@ We also created open-source [ORM benchmarks](https://benchmarks.prisma.io/) comp ### Major performance improvements in almost every release -Prisma ORM has been following a steady and reliable release cadence in cycles of three weeks. If you check out the [release page](https://github.com/prisma/prisma/releases/) of the `prisma/prisma` repo, you'll notice that almost every release came with some kind of performance improvements — be it an optimization of a particular SQL query (as seen in, [5.11.0](https://github.com/prisma/prisma/releases/tag/5.11.0), [5.9.0](https://github.com/prisma/prisma/releases/tag/5.9.0), [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0), [5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0), [5.2.0](https://github.com/prisma/prisma/releases/tag/5.2.0), [5.1.0](https://github.com/prisma/prisma/releases/tag/5.1.0), …), introducing new batch queries like `createManyAndReturn` (in [5.14.0](https://github.com/prisma/prisma/releases/tag/5.14.0)), [speeding up cold starts by 9x](https://www.prisma.io/blog/prisma-and-serverless-73hbgKnZ6t) (in [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0)) or introducing [support for native JS-based drivers](https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV) (in [5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0)). +Prisma ORM has been following a steady and reliable release cadence in cycles of three weeks. If you check out the [release page](https://github.com/prisma/orm/releases/) of the `prisma/prisma` repo, you'll notice that almost every release came with some kind of performance improvements — be it an optimization of a particular SQL query (as seen in, [5.11.0](https://github.com/prisma/orm/releases/tag/5.11.0), [5.9.0](https://github.com/prisma/orm/releases/tag/5.9.0), [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0), [5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0), [5.2.0](https://github.com/prisma/orm/releases/tag/5.2.0), [5.1.0](https://github.com/prisma/orm/releases/tag/5.1.0), …), introducing new batch queries like `createManyAndReturn` (in [5.14.0](https://github.com/prisma/orm/releases/tag/5.14.0)), [speeding up cold starts by 9x](https://www.prisma.io/blog/prisma-and-serverless-73hbgKnZ6t) (in [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0)) or introducing [support for native JS-based drivers](https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV) (in [5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0)). We are also working on rewriting the Rust-based Query Engine from Rust to TypeScript to save some overhead in serialization between language boundaries and are expecting notable performance improvements from this change as well. @@ -63,7 +63,7 @@ Depending on your use case, dataset, schema, and several other factors, one stra > > [High Performance MySQL, 2nd Edition](https://www.oreilly.com/library/view/high-performance-mysql/9780596101718/ch04.html#join_decomposition) | O'Reilly -Up until Prisma ORM [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0), Prisma ORM would always use the application-level JOIN strategy. However, with the 5.7.0 release, we now allow you to pick the best JOIN strategy for your use case, ensuring you can always get the best performance for your queries. +Up until Prisma ORM [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0), Prisma ORM would always use the application-level JOIN strategy. However, with the 5.7.0 release, we now allow you to pick the best JOIN strategy for your use case, ensuring you can always get the best performance for your queries. ### ORM benchmarks: No major performance differences @@ -236,6 +236,6 @@ At Prisma, we strongly value the feedback we receive from our community! While s > If you're curious to learn more about our approach to open-source governance, check out the [Prisma ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto). -We are going to continue our efforts to make Prisma ORM the most performant database library with the best possible DX in the TypeScript ecosystem. Let us know via [GitHub](https://github.com/prisma/prisma), [Discord](https://pris.ly/discord) or [X](https://pris.ly/x) what other improvements you like to see 🙌 +We are going to continue our efforts to make Prisma ORM the most performant database library with the best possible DX in the TypeScript ecosystem. Let us know via [GitHub](https://github.com/prisma/orm), [Discord](https://pris.ly/discord) or [X](https://pris.ly/x) what other improvements you like to see 🙌 If you're excited about Prisma ORM, you can help us clarify these misconceptions by sharing this post whenever you see some of them pop up in the developer community. Also, if there are any more myths you'd like us to bust, [tell us](https://x.com/intent/post?text=hey+%40prisma%2C+bust+this+myth%21+%F0%9F%94%A8%0a%3Cshare+details+the+myth%3E)! diff --git a/apps/blog/content/blog/tracing-launch-announcement-pmk4rlpc0ll/index.mdx b/apps/blog/content/blog/tracing-launch-announcement-pmk4rlpc0ll/index.mdx index a736f69dac..f8915fdf29 100644 --- a/apps/blog/content/blog/tracing-launch-announcement-pmk4rlpc0ll/index.mdx +++ b/apps/blog/content/blog/tracing-launch-announcement-pmk4rlpc0ll/index.mdx @@ -98,8 +98,8 @@ To get started with tracing and metrics: We are eager to hear from you! Try out these features and let us know what you think. -📊 Share your [feedback on tracing](https://github.com/prisma/prisma/issues/14640). +📊 Share your [feedback on tracing](https://github.com/prisma/orm/issues/14640). -📈 Share your [feedback on metrics](https://github.com/prisma/prisma/issues/13579). +📈 Share your [feedback on metrics](https://github.com/prisma/orm/issues/13579). 🚀 If you plan to use these features for mission critical applications, please [contact us](https://prisma-data.typeform.com/to/D91R9T4i) to discuss your use case. diff --git a/apps/blog/content/blog/try-the-new-rust-free-version-of-prisma-orm-early-access/index.mdx b/apps/blog/content/blog/try-the-new-rust-free-version-of-prisma-orm-early-access/index.mdx index 9408b167a4..98fb702164 100644 --- a/apps/blog/content/blog/try-the-new-rust-free-version-of-prisma-orm-early-access/index.mdx +++ b/apps/blog/content/blog/try-the-new-rust-free-version-of-prisma-orm-early-access/index.mdx @@ -19,7 +19,7 @@ Faster, more flexible, better DX: This is what our move from Rust to TypeScript ### TL;DR: The Rust-Free ORM is ready for production-use -Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/prisma/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. +Prisma ORM's core engine has undergone a major shift from the **Rust based query engine** to a leaner **TypeScript/WASM core** (the **Query Compiler**). This [new architecture is now **production-ready** (v6.16+)](https://github.com/prisma/orm/releases/tag/6.16.0) and fundamentally improves your developer experience (DX) and application performance. - **No binary overhead:** The dependency on native Rust binaries is eliminated, drastically simplifying deployment and reducing potential complexity issues. - **Performance:** Get **up to 3.4x faster queries** (by removing cross-language serialization) and a **90% smaller bundle size** (from ~14MB to 1.6 MB). @@ -55,13 +55,13 @@ With all that knowledge, we embarked on a journey of removing Rust from the arch ## Prisma ORM v6.7.0: A new architecture without Rust engines (Early Access) -Following our previous updates, we're excited to release the new, _Rust-free_ architecture in [Early Access](https://www.prisma.io/docs/orm/v7/more/releases#early-access) for PostgreSQL and SQLite with this week's [v6.7.0](http://github.com/prisma/prisma/releases/6.7.0) release. Please try it out and let us know what you think! +Following our previous updates, we're excited to release the new, _Rust-free_ architecture in [Early Access](https://www.prisma.io/docs/orm/v7/more/releases#early-access) for PostgreSQL and SQLite with this week's [v6.7.0](http://github.com/prisma/orm/releases/6.7.0) release. Please try it out and let us know what you think! ### Usage with native JavaScript driver packages The Rust-based query engine used to be responsible for managing database connections via built-in database drivers (that were also written in Rust). That's why, unlike other ORMs, Prisma ORM never required you to install additional packages (like [`pg`](https://node-postgres.com/) or [`better-sqlite3`](https://github.com/WiseLibs/better-sqlite3)). -By moving away from Rust, Prisma ORM also won't have built-in drivers anymore and now depends on a native JS driver to be used. This works via [driver adapters](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) which have been part of Prisma ORM since [v5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0) and are available via the `driverAdapters` Preview feature flag. +By moving away from Rust, Prisma ORM also won't have built-in drivers anymore and now depends on a native JS driver to be used. This works via [driver adapters](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) which have been part of Prisma ORM since [v5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0) and are available via the `driverAdapters` Preview feature flag. ### Getting started with the new Prisma ORM architecture @@ -123,7 +123,7 @@ For details on that, you can check out our recent [article](https://www.prisma.i ## What's next for Prisma ORM? -Prisma ORM is undergoing major changes at the moment. We've announced our [ORM manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) a few months ago with all details about changes to our OSS governance process. Since then, we've been working hard at making Prisma ORM _simpler_, _more robust_, and _more flexible_ with features like the new [`prisma-client` generator,](https://www.prisma.io/docs/orm/v7/prisma-schema/overview/generators#prisma-client-early-access) a [TypeScript-based configuration file](https://www.prisma.io/docs/orm/v7/reference/prisma-config-reference) (called `prisma.config.ts`, and removing magic behaviors, like generating Prisma Client into `node_modules`). Check out our [roadmap](https://github.com/prisma/prisma/issues/26592) to see what's next! +Prisma ORM is undergoing major changes at the moment. We've announced our [ORM manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) a few months ago with all details about changes to our OSS governance process. Since then, we've been working hard at making Prisma ORM _simpler_, _more robust_, and _more flexible_ with features like the new [`prisma-client` generator,](https://www.prisma.io/docs/orm/v7/prisma-schema/overview/generators#prisma-client-early-access) a [TypeScript-based configuration file](https://www.prisma.io/docs/orm/v7/reference/prisma-config-reference) (called `prisma.config.ts`, and removing magic behaviors, like generating Prisma Client into `node_modules`). Check out our [roadmap](https://github.com/prisma/orm/issues/26592) to see what's next! ## Try out Prisma ORM without Rust diff --git a/apps/blog/content/blog/tweets-for-trees-arboreal/index.mdx b/apps/blog/content/blog/tweets-for-trees-arboreal/index.mdx index 5b2df73d1e..cb6140a1f3 100644 --- a/apps/blog/content/blog/tweets-for-trees-arboreal/index.mdx +++ b/apps/blog/content/blog/tweets-for-trees-arboreal/index.mdx @@ -39,7 +39,7 @@ We're calling this initiative **#TweetsForTrees**. Every tweet tagging [@prisma] - Spread the word about Prisma, and tweet using the Prisma username. Some exciting recent announcements include: - The [Migrate GA](https://www.prisma.io/blog/prisma-migrate-ga-b5eno5g08d0b) - The [Prisma Studio GA](https://www.prisma.io/blog) - - Any of the new [Prisma releases](https://github.com/prisma/prisma) (in the month of April we expect to release Prisma 2.21, and 2.22) + - Any of the new [Prisma releases](https://github.com/prisma/orm) (in the month of April we expect to release Prisma 2.21, and 2.22) - You can also see all of the exciting new releases and updates that happened this quarter in our [summary blog post](https://www.prisma.io/blog/whats-new-in-prisma-q1-2021-spjyqp0e2rk1) - Help us spot any tweets we've missed. You can ping us directly when people reference Prisma. diff --git a/apps/blog/content/blog/type-safe-js-with-jsdoc-typeSaf3js/index.mdx b/apps/blog/content/blog/type-safe-js-with-jsdoc-typeSaf3js/index.mdx index c1e29c9615..3b39192952 100644 --- a/apps/blog/content/blog/type-safe-js-with-jsdoc-typeSaf3js/index.mdx +++ b/apps/blog/content/blog/type-safe-js-with-jsdoc-typeSaf3js/index.mdx @@ -302,6 +302,6 @@ Learn more about [Productive Development With Prisma's Zero-Cost Type Safety](ht In summary, JsDoc makes a great tool for code documentation and provide a level of type safety when working with JavaScript. JsDoc also provides an incremental way of adopting types in your application without migrating your codebase to TypeScript. -If you have any questions regarding JsDoc, type safety, code documentation or Prisma, feel free to reach out to us on [X/Twitter](https://pris.ly/x), ask a question on [GitHub](https://github.com/prisma/prisma/discussions). +If you have any questions regarding JsDoc, type safety, code documentation or Prisma, feel free to reach out to us on [X/Twitter](https://pris.ly/x), ask a question on [GitHub](https://github.com/prisma/orm/discussions). diff --git a/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx b/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx index 5a02f21a7b..b13120b7eb 100644 --- a/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx +++ b/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx @@ -144,7 +144,7 @@ Wrote ops.json + migration.json to migrations/20260423T1154_add_users_and_posts/ ## Every operation is verified before and after it runs -Each factory function (`createTable`, `addUnique`, `createIndex`, and so on) returns an operation made up of three parts: a **precheck** that runs before the change, the **execute** step that makes the change, and a **postcheck** that runs after ([see how `createTable` is built](https://github.com/prisma/prisma/blob/main/packages/3-targets/3-targets/postgres/src/core/migrations/operations/tables.ts)). When you run `migration.ts`, those operations are written out to `ops.json`. Here's one operation from the output: +Each factory function (`createTable`, `addUnique`, `createIndex`, and so on) returns an operation made up of three parts: a **precheck** that runs before the change, the **execute** step that makes the change, and a **postcheck** that runs after ([see how `createTable` is built](https://github.com/prisma/orm/blob/main/packages/3-targets/3-targets/postgres/src/core/migrations/operations/tables.ts)). When you run `migration.ts`, those operations are written out to `ops.json`. Here's one operation from the output: ```json { diff --git a/apps/blog/content/blog/vscode-extension-prisma-rust-webassembly/index.mdx b/apps/blog/content/blog/vscode-extension-prisma-rust-webassembly/index.mdx index 9648472c00..8a4ce127b9 100644 --- a/apps/blog/content/blog/vscode-extension-prisma-rust-webassembly/index.mdx +++ b/apps/blog/content/blog/vscode-extension-prisma-rust-webassembly/index.mdx @@ -120,7 +120,7 @@ For Prisma, this is exciting as it is the first time we deploy WebAssembly to pr ## Upgrade today -The new version of the [Prisma extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) is available today as part of the [`3.6.0` release](https://github.com/prisma/prisma/releases/tag/3.6.0). +The new version of the [Prisma extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) is available today as part of the [`3.6.0` release](https://github.com/prisma/orm/releases/tag/3.6.0). Upgrade the extension in VS Code for the same developer experience you love. diff --git a/apps/blog/content/blog/whats-new-in-prisma-q1-2021-spjyqp0e2rk1/index.mdx b/apps/blog/content/blog/whats-new-in-prisma-q1-2021-spjyqp0e2rk1/index.mdx index c068eb50b4..a0c7e832f6 100644 --- a/apps/blog/content/blog/whats-new-in-prisma-q1-2021-spjyqp0e2rk1/index.mdx +++ b/apps/blog/content/blog/whats-new-in-prisma-q1-2021-spjyqp0e2rk1/index.mdx @@ -49,7 +49,7 @@ Learn about everything that has happened in the Prisma ecosystem and community f ## Releases & new features -Our engineers have been hard at work issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we have launched in the last three months. +Our engineers have been hard at work issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we have launched in the last three months. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -71,7 +71,7 @@ npx prisma migrate # for example: npx prisma migrate dev ``` -You can learn more about this in the [release notes](https://github.com/prisma/prisma/releases/tag/2.19.0), the [announcement article](https://www.prisma.io/blog/prisma-migrate-ga-b5eno5g08d0b) and the [video demo](https://www.youtube.com/watch?v=Ac-HWBTtLAU&t=51s&ab_channel=Prisma) by [Daniel](https://twitter.com/daniel2color) and [Tom](https://twitter.com/_tomhoule). +You can learn more about this in the [release notes](https://github.com/prisma/orm/releases/tag/2.19.0), the [announcement article](https://www.prisma.io/blog/prisma-migrate-ga-b5eno5g08d0b) and the [video demo](https://www.youtube.com/watch?v=Ac-HWBTtLAU&t=51s&ab_channel=Prisma) by [Daniel](https://twitter.com/daniel2color) and [Tom](https://twitter.com/_tomhoule). ### Use native database types in the Prisma schema @@ -166,7 +166,7 @@ We regularly add new features to the Prisma Client API to enable more powerful d #### Order by relations (Preview) -Since [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0), you can order the results of `findMany` queries by properties of [related](https://www.prisma.io/docs/concepts/components/prisma-schema/relations) models. For example, you can order a list of posts alphabetically by the names of their authors: +Since [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0), you can order the results of `findMany` queries by properties of [related](https://www.prisma.io/docs/concepts/components/prisma-schema/relations) models. For example, you can order a list of posts alphabetically by the names of their authors: @@ -197,7 +197,7 @@ model User { ``` -Additionaly, the [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0) release makes it possible to order by the aggregates (e.g. count) of relations as well. Here's is an example that orders a list of users by the number of the posts they created: +Additionaly, the [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0) release makes it possible to order by the aggregates (e.g. count) of relations as well. Here's is an example that orders a list of users by the number of the posts they created: @@ -228,7 +228,7 @@ model User { #### Count on relations (Preview) -This [highly requested feature](https://github.com/prisma/prisma/issues/5079) is now Preview since [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0). You can now count the number of related records by passing `_count` to the `select` or `include` options and then specifying which relation counts should be included in the resulting objects via another `select`. +This [highly requested feature](https://github.com/prisma/orm/issues/5079) is now Preview since [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0). You can now count the number of related records by passing `_count` to the `select` or `include` options and then specifying which relation counts should be included in the resulting objects via another `select`. For example, counting the number of posts that an user has written: @@ -255,7 +255,7 @@ const users = await prisma.user.findMany({ #### Efficient bulk creates with `createMany` -The new `createMany` operation (introduced in [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0)) enables you to insert data a whole lot faster: +The new `createMany` operation (introduced in [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0)) enables you to insert data a whole lot faster: ```ts const result = await prisma.user.createMany({ @@ -271,7 +271,7 @@ console.log(`Created ${result.count} users!`) ``` #### Directly set foreign keys -Since [2.15.0](https://github.com/prisma/prisma/releases/tag/2.16.0), it is possible to dirctly set foreign keys instead of wiring up relations via the `connect` API: +Since [2.15.0](https://github.com/prisma/orm/releases/tag/2.16.0), it is possible to dirctly set foreign keys instead of wiring up relations via the `connect` API: ```ts // An example of the new API that directly sets the foreign key @@ -294,7 +294,7 @@ const user = await prisma.profile.create({ ``` #### Group by -Since [2.14.0](https://github.com/prisma/prisma/releases/tag/2.14.0), Prisma Client supports _group by_ queries: +Since [2.14.0](https://github.com/prisma/orm/releases/tag/2.14.0), Prisma Client supports _group by_ queries: @@ -360,7 +360,7 @@ You can learn more about these queries in the [docs](https://www.prisma.io/docs/ #### Reducing overhead between Node.js and Rust with N-API (Preview) -[N-API](https://napi.rs/) is a new technique for binding Prisma's Rust-based [query engine](https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine) directly to Prisma Client that was introduced in [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0). This reduces the communication overhead between the Node.js and Rust layers when resolving Prisma Client's database queries. +[N-API](https://napi.rs/) is a new technique for binding Prisma's Rust-based [query engine](https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine) directly to Prisma Client that was introduced in [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0). This reduces the communication overhead between the Node.js and Rust layers when resolving Prisma Client's database queries. Enabling the N-API will not affect your workflows in any way, the experience of using Prisma will remain exactly the same. @@ -812,7 +812,7 @@ Also, **we are hiring** for various roles! If you're interested in joining us an ## What's next? -The best places to stay up-to-date about what we are currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). +The best places to stay up-to-date about what we are currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). We are currently working on a [connector for MongoDB](https://www.notion.so/prismaio/Support-MongoDB-9f115ebf4a754069a7d7eaae94dc4651) and are hoping to have an Early Access version of it ready in the next three months. diff --git a/apps/blog/content/blog/whats-new-in-prisma-q2-2021-z70muetl386d/index.mdx b/apps/blog/content/blog/whats-new-in-prisma-q2-2021-z70muetl386d/index.mdx index e7206cf005..0813c5059c 100644 --- a/apps/blog/content/blog/whats-new-in-prisma-q2-2021-z70muetl386d/index.mdx +++ b/apps/blog/content/blog/whats-new-in-prisma-q2-2021-z70muetl386d/index.mdx @@ -42,7 +42,7 @@ Learn about everything that has happened in the Prisma ecosystem and community f ## Releases & new features -Our engineers have been hard at work issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we have launched in the last three months. +Our engineers have been hard at work issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we have launched in the last three months. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -65,7 +65,7 @@ You can try it today and we would love to [know your feedback](https://github.co ### Referential Actions now enable cascading deletes and updates (Preview) -Since [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0), we introduced a new feature in [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) which allow you to define cascading delete and update behavior in your Prisma schema. Here’s an example: +Since [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0), we introduced a new feature in [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) which allow you to define cascading delete and update behavior in your Prisma schema. Here’s an example: ```prisma model User { @@ -78,7 +78,7 @@ model Post { author User @relation(fields: [authorId], onDelete: Cascade, onUpdate: Cascade) } ``` -If you run into any questions or have any feedback, we’re available in this [issue](https://github.com/prisma/prisma/issues/7816). +If you run into any questions or have any feedback, we’re available in this [issue](https://github.com/prisma/orm/issues/7816). ### `prisma db push` is now generally available 🚀 @@ -90,7 +90,7 @@ It is now promoted from [Preview](https://www.prisma.io/docs/about/prisma/releas ### Human-readable drift diagnostics for `prisma migrate dev` -Since [2.25.0](https://github.com/prisma/prisma/releases/tag/2.25.0), Database schema drift occurs when your database schema is out of sync with your migration history, i.e. the database schema has drifted away from the source of truth. +Since [2.25.0](https://github.com/prisma/orm/releases/tag/2.25.0), Database schema drift occurs when your database schema is out of sync with your migration history, i.e. the database schema has drifted away from the source of truth. With this release, we improve the way how the drift is printed to the console when detected in the `prisma migrate dev` command. @@ -127,7 +127,7 @@ Learn more about using the .env file in our [documentation](https://www.prisma.i #### MongoDB gets Json and Enum Support -In [2.24.0](https://github.com/prisma/prisma/releases/tag/2.24.0), we added `Json` and `enum` support to the MongoDB provider for Prisma Client. Here's a sample schema with both: +In [2.24.0](https://github.com/prisma/orm/releases/tag/2.24.0), we added `Json` and `enum` support to the MongoDB provider for Prisma Client. Here's a sample schema with both: ```prisma prisma @@ -155,7 +155,7 @@ As a reminder, the mongodb provider is still in [Early Access](https://www.prism #### JSON filtering (preview) -Since [2.23.0](https://github.com/prisma/prisma/releases/tag/2.23.0), you can now filter rows by data inside a Json type. JSON filtering support is available in PostgreSQL and MySQL. +Since [2.23.0](https://github.com/prisma/orm/releases/tag/2.23.0), you can now filter rows by data inside a Json type. JSON filtering support is available in PostgreSQL and MySQL. Assuming we have the following data in a database: @@ -211,7 +211,7 @@ enum Level { #### Order by an aggregate in groupBy (preview) -Since [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0), you can Order by an aggregate in groupBy. Let's say you want to group your users by the city they live in and then order the results by the cities with the most users. +Since [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0), you can Order by an aggregate in groupBy. Let's say you want to group your users by the city they live in and then order the results by the cities with the most users. @@ -547,6 +547,6 @@ Also, **we are hiring** for various roles! If you're interested in joining us an ## What's next? -The best places to stay up-to-date about what we are currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) +The best places to stay up-to-date about what we are currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) -You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. diff --git a/apps/blog/content/blog/why-prisma-orm-checks-types-faster-than-drizzle/index.mdx b/apps/blog/content/blog/why-prisma-orm-checks-types-faster-than-drizzle/index.mdx index 2fe0ccdc1c..39d700093b 100644 --- a/apps/blog/content/blog/why-prisma-orm-checks-types-faster-than-drizzle/index.mdx +++ b/apps/blog/content/blog/why-prisma-orm-checks-types-faster-than-drizzle/index.mdx @@ -335,9 +335,9 @@ As part of our collaboration with David Blass, we also underwent a major optimiz - **`readonly` arrays as the base case**: Prevents inference traps where readonly tuples break assignability to `any[]`. - **Simplified abstractions**: Removed unnecessary utilities that mirrored built-ins or introduced extra indirection without benefit. - **Improved input validation patterns**: Consolidated multi-step generic chains into single mapped-type validators for better readability and performance. -- **Type performance CI tests**: Added CI guardrails that snapshot instantiations/check times to prevent regressions (PR [#26894](https://github.com/prisma/prisma/pull/26894)). +- **Type performance CI tests**: Added CI guardrails that snapshot instantiations/check times to prevent regressions (PR [#26894](https://github.com/prisma/orm/pull/26894)). -If you're curious about the details, you can check out the PRs ([#27775](https://github.com/prisma/prisma/pull/27775) and [#27777](https://github.com/prisma/prisma/pull/27777)) where we implemented the optimizations. +If you're curious about the details, you can check out the PRs ([#27775](https://github.com/prisma/orm/pull/27775) and [#27777](https://github.com/prisma/orm/pull/27777)) where we implemented the optimizations. ## Conclusion: Type safety doesn't have to come at the cost of DX diff --git a/apps/blog/content/blog/wnip-q1-dsk0golh8v/index.mdx b/apps/blog/content/blog/wnip-q1-dsk0golh8v/index.mdx index 924b306e5a..1ad92e5a33 100644 --- a/apps/blog/content/blog/wnip-q1-dsk0golh8v/index.mdx +++ b/apps/blog/content/blog/wnip-q1-dsk0golh8v/index.mdx @@ -56,7 +56,7 @@ Learn about everything in the Prisma ecosystem and community from January to Mar ## Releases & new features -Our engineers have been working hard, issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features. This quarter, we adjusted our release cadence to every three weeks. Here is an overview of the most exciting features we've launched in the last three months. +Our engineers have been working hard, issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features. This quarter, we adjusted our release cadence to every three weeks. Here is an overview of the most exciting features we've launched in the last three months. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -75,7 +75,7 @@ Here are some of the feature highlights we developed over this period: #### Embedded documents support -In [`3.10.0`](https://github.com/prisma/prisma/releases/tag/3.10.0) we introduced support for reading and modifying embedded documents. Embedded documents provide access to a new `type` keyword in your Prisma schema you can use to define composite types. +In [`3.10.0`](https://github.com/prisma/orm/releases/tag/3.10.0) we introduced support for reading and modifying embedded documents. Embedded documents provide access to a new `type` keyword in your Prisma schema you can use to define composite types. ```prisma model Product { @@ -111,13 +111,13 @@ In `3.4.0`, we added preview support for the introspection of embedded documents When introspecting your database, you can switch off the introspection of composite types with `--composite-type-depth=0` or limit the depth level of the analysis with, for example, `--composite-type-depth=2`. -We took this further and updated the type inference behavior for embedded documents with mixed data types on introspection. From version [`3.11.0`](https://github.com/prisma/prisma/releases/tag/3.11.0), Prisma now defaults to a `Json` type for all fields that have mixed data types. +We took this further and updated the type inference behavior for embedded documents with mixed data types on introspection. From version [`3.11.0`](https://github.com/prisma/orm/releases/tag/3.11.0), Prisma now defaults to a `Json` type for all fields that have mixed data types. Prisma will also show a warning on the console and add a comment to the introspected Prisma schema file to clarify where a field has a mixed data type. #### Index support for composite type fields -In [`3.12.0`](https://github.com/prisma/prisma/releases/tag/3.12.0), we added support for adding indexes on embedded document fields in MongoDB. You can now define a normal, unique, or full-text index in your schema. +In [`3.12.0`](https://github.com/prisma/orm/releases/tag/3.12.0), we added support for adding indexes on embedded document fields in MongoDB. You can now define a normal, unique, or full-text index in your schema. ```prisma type Address { @@ -262,7 +262,7 @@ Prisma Client logs queries in the same format as the `mongosh` console. You can #### Filters no longer return `undefined` fields by default -In [`3.11.1`](https://github.com/prisma/prisma/releases/tag/3.11.1), we've changed the data returned when filtering MongoDB documents on `undefined` fields. The new rule is that `undefined` fields are excluded by default unless explicitly filtered for. This allows you to query for `undefined` and `null` values separately. +In [`3.11.1`](https://github.com/prisma/orm/releases/tag/3.11.1), we've changed the data returned when filtering MongoDB documents on `undefined` fields. The new rule is that `undefined` fields are excluded by default unless explicitly filtered for. This allows you to query for `undefined` and `null` values separately. For example, given the following Prisma schema: @@ -436,7 +436,7 @@ model Category { ``` ### Improved connection pooling resiliency -In [`3.12.0`](https://github.com/prisma/prisma/releases/tag/3.12.0), we busted a ghost that has been bugging teams since the early days of the Prisma ORM. Under certain amounts of load, some people reported that the connection pool would sometimes drop connections or deadlock and not recover. +In [`3.12.0`](https://github.com/prisma/orm/releases/tag/3.12.0), we busted a ghost that has been bugging teams since the early days of the Prisma ORM. Under certain amounts of load, some people reported that the connection pool would sometimes drop connections or deadlock and not recover. After many sightings and a lot of head-scratching, we could finally reproduce the issue. This allowed us to narrow down the problem to one of our dependencies and fix the problem. @@ -446,7 +446,7 @@ After many sightings and a lot of head-scratching, we could finally reproduce th CockroachDB support is the product of collaboration with the Cockroach Labs team. You can use Prisma to introspect your existing database with `db pull` and evolve your schema and propagate changes to your database using Prisma Migrate. -Please give it a spin and [let us know what you think](https://github.com/prisma/prisma/issues/11542) to help us iron out the kinks before we push it to General Availability. +Please give it a spin and [let us know what you think](https://github.com/prisma/orm/issues/11542) to help us iron out the kinks before we push it to General Availability. ### Prisma Client logger revamp @@ -530,7 +530,7 @@ await prisma.post.findMany({ Before `3.8.0`, Prisma `$transaction` queries would fail whenever the Data Proxy and Interactive Transactions Preview features were used together. The `interactiveTransactions` and `dataProxy` Preview flags cannot be used together in this release. Generating the Prisma Client when both Preview features are enabled will throw an error. ### Interactive transactions concurrency -We fixed a [number of issues](https://github.com/prisma/prisma/issues/8707) in version `3.9.0` around timeouts and rollbacks when there were concurrent reads and writes. +We fixed a [number of issues](https://github.com/prisma/orm/issues/8707) in version `3.9.0` around timeouts and rollbacks when there were concurrent reads and writes. If you experienced timeouts or your interactive transactions weren't working quite as you expected, give it another go and let us know what you think. You can learn more about Interactive Transactions in our[ documentation](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions-in-preview). @@ -707,8 +707,8 @@ We love seeing laptops decorated with Prisma stickers, so we're shipping them fo [Prisma Day](https://www.prisma.io/day) is back this year, and it'll be on June 15 - 16 at the James&June Sommergarten in Berlin. Join us in-person or online for talks and workshops on modern application development and databases. If you'd like to share your project or give a talk, feel free to [submit a CFP](https://prisma-data.typeform.com/to/Gm9zMrKA). -The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). +The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). -You can also engage in conversations in our [Slack channel](https://slack.prisma.io), and start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io), and start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. If you never want to miss any news from the Prisma community, [follow us on X/Twitter](https://pris.ly/x). diff --git a/apps/blog/content/blog/wnip-q2-2022-pmn7rulcj8x/index.mdx b/apps/blog/content/blog/wnip-q2-2022-pmn7rulcj8x/index.mdx index ade82fb5b6..f752c23490 100644 --- a/apps/blog/content/blog/wnip-q2-2022-pmn7rulcj8x/index.mdx +++ b/apps/blog/content/blog/wnip-q2-2022-pmn7rulcj8x/index.mdx @@ -59,9 +59,9 @@ Learn about everything in the Prisma ecosystem and community from April to July - [What's Next](#whats-next) ## Releases & new features -Our engineers have been working hard, issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). +Our engineers have been working hard, issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). -We once shipped a regression (and fixed it quickly, of course!), a new major version, [Prisma 4](https://github.com/prisma/prisma/releases/tag/4.0.0) coupled with breaking changes, promoted a ton of features to [General Availability](https://www.prisma.io/docs/about/prisma/releases#generally-available-ga), released a couple of new [Preview features](https://www.prisma.io/docs/about/prisma/releases#preview), and improvements in the last three months. +We once shipped a regression (and fixed it quickly, of course!), a new major version, [Prisma 4](https://github.com/prisma/orm/releases/tag/4.0.0) coupled with breaking changes, promoted a ton of features to [General Availability](https://www.prisma.io/docs/about/prisma/releases#generally-available-ga), released a couple of new [Preview features](https://www.prisma.io/docs/about/prisma/releases#preview), and improvements in the last three months. In case you missed it, we held a livestream walking through issues you may run into while upgrading to Prisma 4 and how to fix them! @@ -299,7 +299,7 @@ const prisma = new PrismaClient() const metrics = await prisma.$metrics.json() console.log(metrics) ``` -To learn more, check out the metrics [documentation](https://www.prisma.io/docs/guides/performance-and-optimization/metrics). Give it a try and [let us know what you think](https://github.com/prisma/prisma/issues/13579). +To learn more, check out the metrics [documentation](https://www.prisma.io/docs/guides/performance-and-optimization/metrics). Give it a try and [let us know what you think](https://github.com/prisma/orm/issues/13579). #### Ordering by first and last nulls We also added support for choosing how to sort null values in a query in `4.1.0`. @@ -324,7 +324,7 @@ await prisma.post.findMany({ }, }) ``` -Learn more in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/filtering-and-sorting#sort-with-null-records-first-or-last) and don't hesitate to share your feedback in [this issue](https://github.com/prisma/prisma/issues/14377). +Learn more in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/filtering-and-sorting#sort-with-null-records-first-or-last) and don't hesitate to share your feedback in [this issue](https://github.com/prisma/orm/issues/14377). ### New Prisma Client APIs: `findUniqueOrThrow` and `findFirstOrThrow` @@ -359,7 +359,7 @@ Here's an illustration explaining the architecture of the Data Proxy in your app ![](/wnip-q2-2022-pmn7rulcj8x/imgs/FYqbgQKWIAAjGvu.jpg) -We introduced Prisma Client for Data Proxy in version [`3.3.0`](https://github.com/prisma/prisma/releases/tag/3.3.0) and we have been shipping features, fixes and improvements. +We introduced Prisma Client for Data Proxy in version [`3.3.0`](https://github.com/prisma/orm/releases/tag/3.3.0) and we have been shipping features, fixes and improvements. From `3.15.0`, we shipped the following changes: @@ -592,7 +592,7 @@ Refer to our [system requirements](https://www.prisma.io/docs/reference/system-r Before `4.0.0`, we had inconsistent and large default values (500 for PostgreSQL and 1000 for MySQL) for the `statement_cache_size`. The new shared default value is 100. -If the new default doesn't work for you, please [create an issue](https://github.com/prisma/prisma/issues/new) and use the `statement_cache_size=x` parameter in your connection string to override the default value. +If the new default doesn't work for you, please [create an issue](https://github.com/prisma/orm/issues/new) and use the `statement_cache_size=x` parameter in your connection string to override the default value. #### Renaming of `@prisma/sdk` npm package to `@prisma/internals` @@ -602,7 +602,7 @@ We do not provide API guarantees for `@prisma/internals` as it might need to int This is technically not a breaking change as usage of the `@prisma/sdk` package is neither documented nor supported. -If you're using `@prisma/sdk` (now `@prisma/internals`), it would be helpful if you could help us understand where, how, and why you are using it by giving us feedback in this [GitHub discussion](https://github.com/prisma/prisma/discussions/13877). Your feedback will be valuable to us in defining a better API. +If you're using `@prisma/sdk` (now `@prisma/internals`), it would be helpful if you could help us understand where, how, and why you are using it by giving us feedback in this [GitHub discussion](https://github.com/prisma/orm/discussions/13877). Your feedback will be valuable to us in defining a better API. #### Removal of the internal `schema` property from the generated Prisma Client @@ -615,8 +615,8 @@ To access the `schema` property, you can use the `getDmmf()` method from `@prism We fixed the following issues in `4.1.0` experienced when setting up and tearing down Prisma Client while running tests: -1. Prisma Client now correctly releases memory on Prisma Client instances that are no longer being used. Learn more in this [GitHub issue](https://github.com/prisma/prisma/issues/8989) -2. Reduced CPU usage spikes when disconnecting Prisma Client instances while using Prisma Client. You can learn more in this [GitHub issue](https://github.com/prisma/prisma/issues/12516) +1. Prisma Client now correctly releases memory on Prisma Client instances that are no longer being used. Learn more in this [GitHub issue](https://github.com/prisma/orm/issues/8989) +2. Reduced CPU usage spikes when disconnecting Prisma Client instances while using Prisma Client. You can learn more in this [GitHub issue](https://github.com/prisma/orm/issues/12516) These fixes will allow you to run your tests a little faster! @@ -767,6 +767,6 @@ Also, **we're hiring** for various roles! If you're interested in joining us, ch ## What's Next -The best places to stay up-to-date about what we are currently working on are our [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). +The best places to stay up-to-date about what we are currently working on are our [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). -You can also engage in conversations in our [Slack channel](https://slack.prisma.io) and start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io) and start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. diff --git a/apps/blog/content/blog/wnip-q3-hpk7pyth8v/index.mdx b/apps/blog/content/blog/wnip-q3-hpk7pyth8v/index.mdx index d4f006f42a..23ff4f550d 100644 --- a/apps/blog/content/blog/wnip-q3-hpk7pyth8v/index.mdx +++ b/apps/blog/content/blog/wnip-q3-hpk7pyth8v/index.mdx @@ -45,17 +45,17 @@ Learn about everything that has happened in the Prisma ecosystem and community f ## Releases & new features -[As previously announced](https://www.prisma.io/blog/prisma-adopts-semver-strictly), Prisma has adopted SemVer strictly and we had our first major release during this quarter (version [`3.0.1`](https://github.com/prisma/prisma/releases/tag/3.0.1)), which had some breaking changes. +[As previously announced](https://www.prisma.io/blog/prisma-adopts-semver-strictly), Prisma has adopted SemVer strictly and we had our first major release during this quarter (version [`3.0.1`](https://github.com/prisma/orm/releases/tag/3.0.1)), which had some breaking changes. For all the breaking changes, there are guides and documentation to assist you with the upgrade. During that major release, many Preview features were promoted to General Availability. This means that they are ready for production use and have passed rigorous testing both internally and by the community. -We recommend that you read through the [release notes](https://github.com/prisma/prisma/releases/3.0.1) carefully and make sure that you've correctly upgraded your application. +We recommend that you read through the [release notes](https://github.com/prisma/orm/releases/3.0.1) carefully and make sure that you've correctly upgraded your application. --- -Our engineers have been hard at work issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we've launched in the last three months. +Our engineers have been hard at work issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we've launched in the last three months. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -65,7 +65,7 @@ We're thrilled to announce that Prisma now has Preview support for MongoDB since MongoDB support has passed rigorous testing internally and by the Early Access participants and is now ready for broader testing by the community. However, as a Preview feature, it is not production-ready. To read more about what preview means, check out the maturity levels in the [Prisma docs](https://www.prisma.io/docs/about/prisma/releases#preview). -We would love to know your feedback! If you have any comments or run into any problems we're available in [this issue](https://github.com/prisma/prisma/issues/8241). You can also browse existing issues that have the [MongoDB label](https://github.com/prisma/prisma/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22topic%3A+mongodb%22). +We would love to know your feedback! If you have any comments or run into any problems we're available in [this issue](https://github.com/prisma/orm/issues/8241). You can also browse existing issues that have the [MongoDB label](https://github.com/prisma/orm/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22topic%3A+mongodb%22). ### Microsoft SQL Server and Azure SQL Connector is now Generally Available @@ -74,7 +74,7 @@ We're excited to announce that Prisma support for **Microsoft SQL Server** and * Since we released Prisma Client for General Availability over a year ago with support for PostgreSQL, MySQL, SQLite, and MariaDB, we've heard from thousands of engineers about how the Prisma ORM is helping them be more productive and confident when building data-intensive applications. -After passing rigorous testing internally and by the community over the last year since the [Preview release in version 2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0), we're thrilled to bring Prisma's streamlined developer experience and type safety to developers using **Microsoft SQL Server** and **Azure SQL** in General Availability 🚀. +After passing rigorous testing internally and by the community over the last year since the [Preview release in version 2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0), we're thrilled to bring Prisma's streamlined developer experience and type safety to developers using **Microsoft SQL Server** and **Azure SQL** in General Availability 🚀. ### Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀 @@ -114,7 +114,7 @@ model Cat { ``` Here, you would not be able to delete a `LitterBox` as long as there still is a `Cat` linked to it in your database, because of the `onDelete: Restrict` annotation. If we had written `onDelete: Cascade`, deleting a `LitterBox` would also automatically delete the `Cat`s linked to it. -Referential Actions was first released in [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0) with the `referentialActions` Preview flag. Since then, we've worked to stabilize the feature. +Referential Actions was first released in [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0) with the `referentialActions` Preview flag. Since then, we've worked to stabilize the feature. We're delighted to announce that Referential Actions is now General Available, meaning it is enabled by default. @@ -124,7 +124,7 @@ Relational databases typically ensure integrity between relations with foreign k However, databases like [PlanetScale](https://planetscale.com/) do not support defining foreign keys. To work around this limitation so that you can use Prisma with PlanetScale, we're introducing a new `referentialIntegrity` setting in **Preview.** -This was initially introduced in version `2.24.0` of Prisma with the `planetScaleMode` preview feature and setting. Starting with the [`3.1.1 release`](https://github.com/prisma/prisma/releases/tag/3.1.1) both have been renamed to `referentialIntegrity`. +This was initially introduced in version `2.24.0` of Prisma with the `planetScaleMode` preview feature and setting. Starting with the [`3.1.1 release`](https://github.com/prisma/orm/releases/tag/3.1.1) both have been renamed to `referentialIntegrity`. The setting lets you control whether referential integrity is enforced by the database with foreign keys (default), or by Prisma, by setting `referentialIntegrity = "prisma"`. @@ -151,7 +151,7 @@ After changing `referentialIntegrity` to `prisma`, make sure you run `prisma gen Note that Referential Integrity is set to `prisma` by default when using MongoDB. -Learn more about it in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode), and [share your feedback](https://github.com/prisma/prisma/issues/9380). +Learn more about it in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode), and [share your feedback](https://github.com/prisma/orm/issues/9380). ### Named Constraints @@ -165,7 +165,7 @@ Additionally, a new convention for default constraint names is now built into th ### Seeding with `prisma db seed` has been revamped and is now Generally Available -When developing locally, it's common to seed your database with initial data to test functionality. In [version 2.15](https://github.com/prisma/prisma/releases/tag/2.15.0) of Prisma, we initially introduced a Preview version of seeding using the `prisma db seed` command. +When developing locally, it's common to seed your database with initial data to test functionality. In [version 2.15](https://github.com/prisma/orm/releases/tag/2.15.0) of Prisma, we initially introduced a Preview version of seeding using the `prisma db seed` command. We're excited to share that the `prisma db seed` command has been revamped and simplified with a better developer experience and is now Generally Available. @@ -235,7 +235,7 @@ Node-API is a new technique for binding Prisma's Rust-based query engine directl Earlier versions of Prisma (since version 2.0.0) used the Prisma Query Engine binary, which runs as a sidecar process alongside your application and handles the heavy lifting of executing queries from Prisma Client against your database. -In [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) we introduced a Preview feature, the Node-API library, as a more efficient way to communicate with the Prisma Engine binary. Using the Node-API library is functionally identical to running the Prisma engine binary while reducing the runtime overhead by making direct binary calls from Node.js. +In [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) we introduced a Preview feature, the Node-API library, as a more efficient way to communicate with the Prisma Engine binary. Using the Node-API library is functionally identical to running the Prisma engine binary while reducing the runtime overhead by making direct binary calls from Node.js. **Starting with the 3.0.1 release we're making the Node-API library engine the default query engine type.** If necessary for your project, you can [fall back to the previous behavior](https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine#configuring-the-query-engine) of a sidecar Prisma Engine binary, however, we don't anticipate a reason to do so. @@ -287,9 +287,9 @@ model Post { ``` -Order by Aggregate Group was initially released as a Preview feature in [2.21.0](https://github.com/prisma/prisma/releases/2.21.0). +Order by Aggregate Group was initially released as a Preview feature in [2.21.0](https://github.com/prisma/orm/releases/2.21.0). -**Starting with the [`3.0.1` release](https://github.com/prisma/prisma/releases/tag/3.0.1) release it is Generally Available 🤩** +**Starting with the [`3.0.1` release](https://github.com/prisma/orm/releases/tag/3.0.1) release it is Generally Available 🤩** If you've been using this Preview feature, you can remove the `orderByAggregateGroup` flag from `previewFeatures` in your Prisma Schema. @@ -341,7 +341,7 @@ await prisma.post.findMany({ ``` -Order by Relation was initially released in Preview in [2.16.0](https://github.com/prisma/prisma/releases/2.16.0). +Order by Relation was initially released in Preview in [2.16.0](https://github.com/prisma/orm/releases/2.16.0). Starting with the `3.0.1` release it is Generally Available 🧙 @@ -462,12 +462,12 @@ const result = await prisma.post.findMany({ ``` -You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://github.com/prisma/prisma/issues/8877). +You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://github.com/prisma/orm/issues/8877). #### Interactive transactions are now in Preview -One of our most debated [feature requests](https://github.com/prisma/prisma/issues/1844)- Interactive Transactions, is now in Preview. +One of our most debated [feature requests](https://github.com/prisma/orm/issues/1844)- Interactive Transactions, is now in Preview. Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability. @@ -483,7 +483,7 @@ generator client { ``` Note that the interactive transactions API does not support controlling isolation levels or locking for now. -You can find out more about implementing use cases with transactions in [the docs](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions), and [share your feedback](https://github.com/prisma/prisma/issues/8664). +You can find out more about implementing use cases with transactions in [the docs](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions), and [share your feedback](https://github.com/prisma/orm/issues/8664). We regularly add new features to the Prisma Client API to enable more powerful database queries that were previously only possible via plain SQL and the `$queryRaw` escape hatch. @@ -817,6 +817,6 @@ We love seeing laptops that are decorated with Prisma stickers, so we're shippin ## What's next? -The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) +The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) -You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. diff --git a/apps/blog/content/blog/wnip-q4-2022-f66prwkjx72s/index.mdx b/apps/blog/content/blog/wnip-q4-2022-f66prwkjx72s/index.mdx index bc248cc7a3..d2f46dd068 100644 --- a/apps/blog/content/blog/wnip-q4-2022-f66prwkjx72s/index.mdx +++ b/apps/blog/content/blog/wnip-q4-2022-f66prwkjx72s/index.mdx @@ -54,7 +54,7 @@ Here’s all you need to know about the Prisma ecosystem and community from Augu ## Releases & new features -Our engineers have been working hard, issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features. Here is an overview of what we've launched lately. +Our engineers have been working hard, issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features. Here is an overview of what we've launched lately. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -66,8 +66,8 @@ You can stay up-to-date about all upcoming features on our [roadmap](https://pri Here are some of the feature highlights we've built: -- Support for defining [transaction isolation levels](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#transaction-isolation-level) — from [`4.2.0`](https://github.com/prisma/prisma/releases/tag/4.2.0) -- Support for the Prisma Data Proxy — from [`4.6.0`](https://github.com/prisma/prisma/releases/tag/4.6.0) +- Support for defining [transaction isolation levels](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#transaction-isolation-level) — from [`4.2.0`](https://github.com/prisma/orm/releases/tag/4.2.0) +- Support for the Prisma Data Proxy — from [`4.6.0`](https://github.com/prisma/orm/releases/tag/4.6.0) Here's an example of an interactive transaction with a `Serializable` isolation level: @@ -89,9 +89,9 @@ You can now remove the `interactiveTransactions` Preview feature in your schem `relationMode="prisma"` is now stable for our users working with databases that don't rely on foreign keys to manage relations. 🎉 -Prisma’s [relation mode](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode) started as a way to support PlanetScale which does not allow you to create foreign keys for better online migration support. We transformed that into our *Referential Integrity Emulation* in [`3.1.1`](https://github.com/prisma/prisma/releases/tag/3.1.1) when we realised that more users could benefit from it, and then integrated it as the default mode for MongoDB, which generally does not *have* foreign keys. Prisma needed to use emulation to give the same guarantees. +Prisma’s [relation mode](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode) started as a way to support PlanetScale which does not allow you to create foreign keys for better online migration support. We transformed that into our *Referential Integrity Emulation* in [`3.1.1`](https://github.com/prisma/orm/releases/tag/3.1.1) when we realised that more users could benefit from it, and then integrated it as the default mode for MongoDB, which generally does not *have* foreign keys. Prisma needed to use emulation to give the same guarantees. -We then realized the feature was more than just referential integrity and affected how relations work. To reflect this, we renamed the feature to relation mode and the `datasource` property to `relationMode` in [`4.5.0`](https://github.com/prisma/prisma/releases/tag/4.5.0) +We then realized the feature was more than just referential integrity and affected how relations work. To reflect this, we renamed the feature to relation mode and the `datasource` property to `relationMode` in [`4.5.0`](https://github.com/prisma/orm/releases/tag/4.5.0) #### Index warnings for `relationMode = "prisma"` @@ -125,10 +125,10 @@ For more information, check out our [updated relation mode documentation](https #### Prisma Client improvements -- **`extendedWhereUnique` improvements** ––– in [`4.5.0`](https://github.com/prisma/prisma/releases/tag/4.5.0), we introduced this Preview feature to allow filtering for non-unique properties in unique where queries. We added new rules to decide when concurrent `findUnique` queries get batched into a `findMany` query. Let us know your thoughts and share your feedback on [the Preview feature](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) in this [GitHub issue](https://github.com/prisma/prisma/issues/15837). -- **`fieldReference`** ––– [field references](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#compare-columns-in-the-same-table) support on query filters will allow you to compare columns against other columns. To enable column comparisons in the same table, add the `fieldReference` feature flag to the `generator` block of your Prisma Schema. Try it out and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/15068). -- **`filteredRelationCount`** ––– we've added support for the ability to count by a filtered relation. You can enable this feature by adding the `filteredRelationCount` Preview feature flag. Learn more in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#filter-the-relation-count) and let us know what you think in [this issue](https://github.com/prisma/prisma/issues/15069). -- **[Deno](https://deno.land/) for Prisma Client for Data Proxy** ––– we have released initial support for this feature in collaboration with the amazing team at Deno 🦕. To use Prisma Client in a Deno project, add the `deno` Preview feature flag to your Prisma schema and define a folder as `output` (this is required for Deno). Read [this guide in our documentation for a full example and individual steps](https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-deno-deploy). For feedback, please comment on this [GitHub issue](https://github.com/prisma/prisma/issues/15844). +- **`extendedWhereUnique` improvements** ––– in [`4.5.0`](https://github.com/prisma/orm/releases/tag/4.5.0), we introduced this Preview feature to allow filtering for non-unique properties in unique where queries. We added new rules to decide when concurrent `findUnique` queries get batched into a `findMany` query. Let us know your thoughts and share your feedback on [the Preview feature](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) in this [GitHub issue](https://github.com/prisma/orm/issues/15837). +- **`fieldReference`** ––– [field references](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#compare-columns-in-the-same-table) support on query filters will allow you to compare columns against other columns. To enable column comparisons in the same table, add the `fieldReference` feature flag to the `generator` block of your Prisma Schema. Try it out and let us know what you think in this [GitHub issue](https://github.com/prisma/orm/issues/15068). +- **`filteredRelationCount`** ––– we've added support for the ability to count by a filtered relation. You can enable this feature by adding the `filteredRelationCount` Preview feature flag. Learn more in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#filter-the-relation-count) and let us know what you think in [this issue](https://github.com/prisma/orm/issues/15069). +- **[Deno](https://deno.land/) for Prisma Client for Data Proxy** ––– we have released initial support for this feature in collaboration with the amazing team at Deno 🦕. To use Prisma Client in a Deno project, add the `deno` Preview feature flag to your Prisma schema and define a folder as `output` (this is required for Deno). Read [this guide in our documentation for a full example and individual steps](https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-deno-deploy). For feedback, please comment on this [GitHub issue](https://github.com/prisma/orm/issues/15844). #### Prisma Client extensions @@ -143,7 +143,7 @@ Read about how [Prisma Client just became a lot more flexible](https://www.prism -We're excited to see what you build with them! For more information, check out our [docs](https://www.prisma.io/docs/concepts/components/prisma-client/client-extensions) and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/16500). +We're excited to see what you build with them! For more information, check out our [docs](https://www.prisma.io/docs/concepts/components/prisma-client/client-extensions) and let us know what you think in this [GitHub issue](https://github.com/prisma/orm/issues/16500). #### Multi-schema support for CockroachDB and PostgreSQL The ability to query and manage multiple database schemas has been a long-standing feature request from our community. We've now added [Preview support](https://www.prisma.io/docs/about/prisma/releases#preview) for multi-schema for CockroachDB and PostgreSQL. 🎉 @@ -157,7 +157,7 @@ If you already have a CockroachDB or a PostgreSQL database using multiple 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://www.prisma.io/docs/guides/other/multi-schema) and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/15077). +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://www.prisma.io/docs/guides/other/multi-schema) and let us know what you think in this [GitHub issue](https://github.com/prisma/orm/issues/15077). #### PostgreSQL extension management We’ve added support for declaring PostgreSQL extensions in the Prisma schema. The feature comes with support for introspection and migrations. You can now adopt, evolve and manage which PostgreSQL database extensions are installed directly from within your Prisma schema. @@ -179,7 +179,7 @@ datasource db { ``` > ⚠️ To avoid noise from introspection, we currently only introspect the following allow-list: citext, pgcrypto, uuid-ossp, and postgis. But you can add and configure any extension to your Prisma schema manually. -Please visit our [documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/postgresql-extensions) to learn more about this feature or leave a comment with feedback on the GitHub [issue](https://github.com/prisma/prisma/issues/15835). +Please visit our [documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/postgresql-extensions) to learn more about this feature or leave a comment with feedback on the GitHub [issue](https://github.com/prisma/orm/issues/15835). #### Prisma Client tracing support @@ -191,7 +191,7 @@ With tracing, you can now see how long Prisma takes and what queries are issued Read more about tracing in our [announcement post](https://www.prisma.io/blog/tracing-launch-announcement-pmk4rlpc0ll) and learn more in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/opentelemetry-tracing) on how to start working with tracing. -Try it out and [let us know what you think](https://github.com/prisma/prisma/issues/14640). +Try it out and [let us know what you think](https://github.com/prisma/orm/issues/14640). ### General improvements @@ -199,11 +199,11 @@ Try it out and [let us know what you think](https://github.com/prisma/prisma/is 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. -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. Read more about it in the [`4.8.0` release notes](https://github.com/prisma/prisma/releases/tag/4.8.0). +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. Read more about it in the [`4.8.0` release notes](https://github.com/prisma/orm/releases/tag/4.8.0). #### 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. You can read more details about it in this GitHub [comment](https://github.com/prisma/prisma/issues/16553#issuecomment-1353302617). +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. You can read more details about it in this GitHub [comment](https://github.com/prisma/orm/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. @@ -211,7 +211,7 @@ We also have rewritten our OpenSSL version detection logic, making it future-pro [Prisma’s `upsert`](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#upsert) is one of its most powerful and most convenient APIs. Prisma will now default to the native database upsert for PostgreSQL, SQLite, and CockroachDB whenever possible. -Get more details in the [`4.6.0` release notes](https://github.com/prisma/prisma/releases/tag/4.6.0) and try it out. If you run into any issues, don't hesitate to create a [GitHub issue](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml). +Get more details in the [`4.6.0` release notes](https://github.com/prisma/orm/releases/tag/4.6.0) and try it out. If you run into any issues, don't hesitate to create a [GitHub issue](https://github.com/prisma/orm/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml). #### Prisma CLI exit code fixes @@ -228,9 +228,9 @@ We've made several improvements to the Prisma CLI: #### `prisma format` now uses a Wasm module -Initially, the `prisma format` command relied on logic from the Prisma engines in form of a native binary. After the [`4.3.0` release](https://github.com/prisma/prisma/releases/tag/4.3.0), `prisma format` will be using the same Wasm module as the one the Prisma language server uses, i.e. `@prisma/prisma-fmt-wasm`, which is now visible in `prisma version` command's output. +Initially, the `prisma format` command relied on logic from the Prisma engines in form of a native binary. After the [`4.3.0` release](https://github.com/prisma/orm/releases/tag/4.3.0), `prisma format` will be using the same Wasm module as the one the Prisma language server uses, i.e. `@prisma/prisma-fmt-wasm`, which is now visible in `prisma version` command's output. -Let us know what you think. In case you run into any issues, create a [GitHub issue](https://github.com/prisma/prisma). +Let us know what you think. In case you run into any issues, create a [GitHub issue](https://github.com/prisma/orm). #### MongoDB query fixes @@ -238,8 +238,8 @@ Let us know what you think. In case you run into any issues, create a [GitHub i While implementing field reference support, we noticed a few correctness bugs in our MongoDB connector that we fixed along the way: -1. `mode: insensitive` alphanumeric comparisons (e.g. “a” > “Z”) didn’t work ([GitHub issue](https://github.com/prisma/prisma/issues/14663)) -2. `mode: insensitive` didn’t exclude undefined ([GitHub issue](https://github.com/prisma/prisma/issues/14664)) +1. `mode: insensitive` alphanumeric comparisons (e.g. “a” > “Z”) didn’t work ([GitHub issue](https://github.com/prisma/orm/issues/14663)) +2. `mode: insensitive` didn’t exclude undefined ([GitHub issue](https://github.com/prisma/orm/issues/14664)) 3. `isEmpty: false` on lists types (e.g. String[]) returned true when a list is empty ([GitHub issue](https://github.com/prisma/prisma-engines/issues/3133)) 4. `hasEvery` on list types wasn’t aligned with the SQL implementations ([GitHub issue](https://github.com/prisma/prisma-engines/issues/3132)) @@ -297,7 +297,7 @@ We've renamed the metrics — counters, gauges, and histograms — returned from | `pool_idle_connections` | `prisma_pool_connections_idle` | | `pool_wait_count` | `prisma_client_queries_wait` | -Give Prisma Client `metrics` a shot and let us know what you think in this [GitHub issue](https://github.com/prisma/prisma/issues/13579) +Give Prisma Client `metrics` a shot and let us know what you think in this [GitHub issue](https://github.com/prisma/orm/issues/13579) To learn more, check out [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/metrics). @@ -313,9 +313,9 @@ If you are interested in having this supported, let us know in this [GitHub iss #### Experimental Cloudflare Module Worker support -We fixed a bug that prevented the [Prisma Edge Client](https://www.prisma.io/docs/data-platform/data-proxy#edge-runtimes) from working with [Cloudflare Module Workers](https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/). We now provide experimental support with a [workaround for environment variables](https://github.com/prisma/prisma/issues/13771#issuecomment-1204295665). +We fixed a bug that prevented the [Prisma Edge Client](https://www.prisma.io/docs/data-platform/data-proxy#edge-runtimes) from working with [Cloudflare Module Workers](https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/). We now provide experimental support with a [workaround for environment variables](https://github.com/prisma/orm/issues/13771#issuecomment-1204295665). -Try it out and let us know how what you think! In case you run into any errors, feel free to create a [bug report](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml). +Try it out and let us know how what you think! In case you run into any errors, feel free to create a [bug report](https://github.com/prisma/orm/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.yml). #### Fixed “Invalid string length” error in Prisma Studio and Prisma Data Platform Data Browser @@ -325,7 +325,7 @@ Many people were having issues with an ["Invalid string length" error](https:// When using certain isolation levels, it is expected that a transaction can fail due to a write conflict or a deadlock, throwing an error. One way to solve these cases is by retrying the transaction. -To make this easier, we're introducing a new [`PrismaClientKnownRequestError`](https://www.prisma.io/docs/reference/api-reference/error-reference#prismaclientknownrequesterror) with the [error code `P2034`](https://www.prisma.io/docs/reference/api-reference/error-reference#p2034): "Transaction failed due to a write conflict or a deadlock. Please retry your transaction". You can programmatically catch the error and retry the transaction. Check out the [`4.4.0` release notes](https://github.com/prisma/prisma/releases/tag/4.4.0) for further details here and examples. +To make this easier, we're introducing a new [`PrismaClientKnownRequestError`](https://www.prisma.io/docs/reference/api-reference/error-reference#prismaclientknownrequesterror) with the [error code `P2034`](https://www.prisma.io/docs/reference/api-reference/error-reference#p2034): "Transaction failed due to a write conflict or a deadlock. Please retry your transaction". You can programmatically catch the error and retry the transaction. Check out the [`4.4.0` release notes](https://github.com/prisma/orm/releases/tag/4.4.0) for further details here and examples. ## Community We wouldn't be where we are today without our amazing [community](https://www.prisma.io/community) of developers. Our [Slack](https://slack.prisma.io) has almost 50k members and is a great place to ask questions, share feedback and initiate discussions around Prisma. @@ -525,6 +525,6 @@ Also, **we're hiring** for various roles! If you're interested in joining us, --- ## What’s next? -The best places to stay up-to-date about what we are currently working on are our [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). +The best places to stay up-to-date about what we are currently working on are our [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). -You can also engage in conversations in our [Slack channel](https://slack.prisma.io/) and start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io/) and start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. diff --git a/apps/blog/content/blog/wnip-q4-dsk0golh8v/index.mdx b/apps/blog/content/blog/wnip-q4-dsk0golh8v/index.mdx index 76a88c375b..b2ace481e2 100644 --- a/apps/blog/content/blog/wnip-q4-dsk0golh8v/index.mdx +++ b/apps/blog/content/blog/wnip-q4-dsk0golh8v/index.mdx @@ -45,17 +45,17 @@ Learn about everything that has happened in the Prisma ecosystem and community f ## Releases & new features -[As previously announced](https://www.prisma.io/blog/prisma-adopts-semver-strictly), Prisma has adopted SemVer strictly and we had our first major release during this quarter (version [`3.0.1`](https://github.com/prisma/prisma/releases/tag/3.0.1)), which had some breaking changes. +[As previously announced](https://www.prisma.io/blog/prisma-adopts-semver-strictly), Prisma has adopted SemVer strictly and we had our first major release during this quarter (version [`3.0.1`](https://github.com/prisma/orm/releases/tag/3.0.1)), which had some breaking changes. For all the breaking changes, there are guides and documentation to assist you with the upgrade. During that major release, many Preview features were promoted to General Availability. This means that they are ready for production use and have passed rigorous testing both internally and by the community. -We recommend that you read through the [release notes](https://github.com/prisma/prisma/releases/3.0.1) carefully and make sure that you've correctly upgraded your application. +We recommend that you read through the [release notes](https://github.com/prisma/orm/releases/3.0.1) carefully and make sure that you've correctly upgraded your application. --- -Our engineers have been hard at work issuing new [releases](https://github.com/prisma/prisma/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we've launched in the last three months. +Our engineers have been hard at work issuing new [releases](https://github.com/prisma/orm/releases/) with many improvements and new features every two weeks. Here is an overview of the most exciting features that we've launched in the last three months. You can stay up-to-date about all upcoming features on our [roadmap](https://pris.ly/roadmap). @@ -65,7 +65,7 @@ We're thrilled to announce that Prisma now has Preview support for MongoDB since MongoDB support has passed rigorous testing internally and by the Early Access participants and is now ready for broader testing by the community. However, as a Preview feature, it is not production-ready. To read more about what preview means, check out the maturity levels in the [Prisma docs](https://www.prisma.io/docs/about/prisma/releases#preview). -We would love to know your feedback! If you have any comments or run into any problems we're available in [this issue](https://github.com/prisma/prisma/issues/8241). You can also browse existing issues that have the [MongoDB label](https://github.com/prisma/prisma/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22topic%3A+mongodb%22). +We would love to know your feedback! If you have any comments or run into any problems we're available in [this issue](https://github.com/prisma/orm/issues/8241). You can also browse existing issues that have the [MongoDB label](https://github.com/prisma/orm/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22topic%3A+mongodb%22). ### Microsoft SQL Server and Azure SQL Connector is now Generally Available @@ -74,7 +74,7 @@ We're excited to announce that Prisma support for **Microsoft SQL Server** and * Since we released Prisma Client for General Availability over a year ago with support for PostgreSQL, MySQL, SQLite, and MariaDB, we've heard from thousands of engineers about how the Prisma ORM is helping them be more productive and confident when building data-intensive applications. -After passing rigorous testing internally and by the community over the last year since the [Preview release in version 2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0), we're thrilled to bring Prisma's streamlined developer experience and type safety to developers using **Microsoft SQL Server** and **Azure SQL** in General Availability 🚀. +After passing rigorous testing internally and by the community over the last year since the [Preview release in version 2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0), we're thrilled to bring Prisma's streamlined developer experience and type safety to developers using **Microsoft SQL Server** and **Azure SQL** in General Availability 🚀. ### Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀 @@ -114,7 +114,7 @@ model Cat { ``` Here, you would not be able to delete a `LitterBox` as long as there still is a `Cat` linked to it in your database, because of the `onDelete: Restrict` annotation. If we had written `onDelete: Cascade`, deleting a `LitterBox` would also automatically delete the `Cat`s linked to it. -Referential Actions was first released in [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0) with the `referentialActions` Preview flag. Since then, we've worked to stabilize the feature. +Referential Actions was first released in [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0) with the `referentialActions` Preview flag. Since then, we've worked to stabilize the feature. We're delighted to announce that Referential Actions is now General Available, meaning it is enabled by default. @@ -124,7 +124,7 @@ Relational databases typically ensure integrity between relations with foreign k However, databases like [PlanetScale](https://planetscale.com/) do not support defining foreign keys. To work around this limitation so that you can use Prisma with PlanetScale, we're introducing a new `referentialIntegrity` setting in **Preview.** -This was initially introduced in version `2.24.0` of Prisma with the `planetScaleMode` preview feature and setting. Starting with the [`3.1.1 release`](https://github.com/prisma/prisma/releases/tag/3.1.1) both have been renamed to `referentialIntegrity`. +This was initially introduced in version `2.24.0` of Prisma with the `planetScaleMode` preview feature and setting. Starting with the [`3.1.1 release`](https://github.com/prisma/orm/releases/tag/3.1.1) both have been renamed to `referentialIntegrity`. The setting lets you control whether referential integrity is enforced by the database with foreign keys (default), or by Prisma, by setting `referentialIntegrity = "prisma"`. @@ -151,7 +151,7 @@ After changing `referentialIntegrity` to `prisma`, make sure you run `prisma gen Note that Referential Integrity is set to `prisma` by default when using MongoDB. -Learn more about it in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode), and [share your feedback](https://github.com/prisma/prisma/issues/9380). +Learn more about it in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode), and [share your feedback](https://github.com/prisma/orm/issues/9380). ### Named Constraints @@ -165,7 +165,7 @@ Additionally, a new convention for default constraint names is now built into th ### Seeding with `prisma db seed` has been revamped and is now Generally Available -When developing locally, it's common to seed your database with initial data to test functionality. In [version 2.15](https://github.com/prisma/prisma/releases/tag/2.15.0) of Prisma, we initially introduced a Preview version of seeding using the `prisma db seed` command. +When developing locally, it's common to seed your database with initial data to test functionality. In [version 2.15](https://github.com/prisma/orm/releases/tag/2.15.0) of Prisma, we initially introduced a Preview version of seeding using the `prisma db seed` command. We're excited to share that the `prisma db seed` command has been revamped and simplified with a better developer experience and is now Generally Available. @@ -234,7 +234,7 @@ Node-API is a new technique for binding Prisma's Rust-based query engine directl Earlier versions of Prisma (since version 2.0.0) used the Prisma Query Engine binary, which runs as a sidecar process alongside your application and handles the heavy lifting of executing queries from Prisma Client against your database. -In [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) we introduced a Preview feature, the Node-API library, as a more efficient way to communicate with the Prisma Engine binary. Using the Node-API library is functionally identical to running the Prisma engine binary while reducing the runtime overhead by making direct binary calls from Node.js. +In [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) we introduced a Preview feature, the Node-API library, as a more efficient way to communicate with the Prisma Engine binary. Using the Node-API library is functionally identical to running the Prisma engine binary while reducing the runtime overhead by making direct binary calls from Node.js. **Starting with the 3.0.1 release we're making the Node-API library engine the default query engine type.** If necessary for your project, you can [fall back to the previous behavior](https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine#configuring-the-query-engine) of a sidecar Prisma Engine binary, however, we don't anticipate a reason to do so. @@ -286,9 +286,9 @@ model Post { ``` -Order by Aggregate Group was initially released as a Preview feature in [2.21.0](https://github.com/prisma/prisma/releases/2.21.0). +Order by Aggregate Group was initially released as a Preview feature in [2.21.0](https://github.com/prisma/orm/releases/2.21.0). -**Starting with the [`3.0.1` release](https://github.com/prisma/prisma/releases/tag/3.0.1) release it is Generally Available 🤩** +**Starting with the [`3.0.1` release](https://github.com/prisma/orm/releases/tag/3.0.1) release it is Generally Available 🤩** If you've been using this Preview feature, you can remove the `orderByAggregateGroup` flag from `previewFeatures` in your Prisma Schema. @@ -337,7 +337,7 @@ await prisma.post.findMany({ ``` -Order by Relation was initially released in Preview in [2.16.0](https://github.com/prisma/prisma/releases/2.16.0). +Order by Relation was initially released in Preview in [2.16.0](https://github.com/prisma/orm/releases/2.16.0). Starting with the `3.0.1` release it is Generally Available 🧙 @@ -459,12 +459,12 @@ const result = await prisma.post.findMany({ ``` -You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://github.com/prisma/prisma/issues/8877). +You can learn more about how the query format works in [our documentation](https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search). We would love to know your feedback! If you have any comments or run into any problems we're available in this [in this Github issue](https://github.com/prisma/orm/issues/8877). #### Interactive transactions are now in Preview -One of our most debated [feature requests](https://github.com/prisma/prisma/issues/1844)- Interactive Transactions, is now in Preview. +One of our most debated [feature requests](https://github.com/prisma/orm/issues/1844)- Interactive Transactions, is now in Preview. Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability. @@ -480,7 +480,7 @@ generator client { ``` Note that the interactive transactions API does not support controlling isolation levels or locking for now. -You can find out more about implementing use cases with transactions in [the docs](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions), and [share your feedback](https://github.com/prisma/prisma/issues/8664). +You can find out more about implementing use cases with transactions in [the docs](https://www.prisma.io/docs/concepts/components/prisma-client/transactions#interactive-transactions), and [share your feedback](https://github.com/prisma/orm/issues/8664). We regularly add new features to the Prisma Client API to enable more powerful database queries that were previously only possible via plain SQL and the `$queryRaw` escape hatch. @@ -814,6 +814,6 @@ We love seeing laptops that are decorated with Prisma stickers, so we're shippin ## What's next? -The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/prisma/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) +The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/prisma/orm/issues) and our public [roadmap](https://pris.ly/roadmap). (Mongo DB support coming soon 👀) -You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/prisma/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. +You can also engage in conversations in our [Slack channel](https://slack.prisma.io), start a discussion on [GitHub](https://github.com/prisma/orm/discussions) or join one of the many [Prisma meetups](https://www.prisma.io/community) around the world. diff --git a/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx b/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx index d39f0a76ad..566e09d7f3 100644 --- a/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx +++ b/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx @@ -360,7 +360,7 @@ Yes. An embedding is just an array of numbers, so you can insert hand-made vecto ## Recap - Embeddings are vectors; semantic search is ordering by the angle between them. pgvector gives Postgres a `vector(N)` column type and a `<=>` cosine distance operator. -- [`@prisma/orm-extension-pgvector`](https://github.com/prisma/prisma/tree/main/packages/3-extensions/pgvector) is a Prisma 8 extension pack: a codec (`Vector<4>` in your types), typed `cosineDistance`/`cosineSimilarity` operations, and a baseline migration that installs the extension for you. +- [`@prisma/orm-extension-pgvector`](https://github.com/prisma/orm/tree/main/packages/3-extensions/pgvector) is a Prisma 8 extension pack: a codec (`Vector<4>` in your types), typed `cosineDistance`/`cosineSimilarity` operations, and a baseline migration that installs the extension for you. - The demo ran on a throwaway database from `npx create-db@latest`, and the whole flow is four commands: `contract emit`, `migration plan`, `db init`, `bun index.ts`. - Fit: apps already on Postgres with up to a few million vectors that want embeddings, filters, and transactions in one place. Reach for a dedicated engine when extreme-scale ANN or full search-engine features are the product. diff --git a/apps/docs/content/docs/(index)/full-stack-tutorial.mdx b/apps/docs/content/docs/(index)/full-stack-tutorial.mdx index cfe303b026..908a442802 100644 --- a/apps/docs/content/docs/(index)/full-stack-tutorial.mdx +++ b/apps/docs/content/docs/(index)/full-stack-tutorial.mdx @@ -56,14 +56,14 @@ Start with the declaration, because it is what every later command operates on. ```ts title="module.ts" import { module } from "@prisma/composer"; -import { pnPostgres } from "@prisma/composer-prisma-cloud/prisma-next"; +import { postgres } from "@prisma/composer-prisma-cloud/orm"; import { appContract } from "./src/prisma/composer.ts"; import app from "./service.ts"; export default module("my-app", ({ provision }) => { const database = provision( - pnPostgres({ + postgres({ name: "database", contract: appContract, config: "./prisma.config.ts", @@ -80,14 +80,14 @@ export default module("my-app", ({ provision }) => { ```ts title="service.ts" import node from "@prisma/composer/node"; import { compute } from "@prisma/composer-prisma-cloud"; -import { pnPostgres } from "@prisma/composer-prisma-cloud/prisma-next"; +import { postgres } from "@prisma/composer-prisma-cloud/orm"; import { appContract } from "./src/prisma/composer.ts"; export default compute({ name: "app", deps: { - database: pnPostgres(appContract), + database: postgres(appContract), }, build: node({ module: import.meta.url, entry: "./dist/server.mjs" }), }); diff --git a/apps/docs/content/docs/ai/prompts/prisma-7.mdx b/apps/docs/content/docs/ai/prompts/prisma-7.mdx index 6a0bc16c09..a26891ea5c 100644 --- a/apps/docs/content/docs/ai/prompts/prisma-7.mdx +++ b/apps/docs/content/docs/ai/prompts/prisma-7.mdx @@ -395,7 +395,7 @@ export const SuggestionStatus = { ### Known Bug (as of v7.2.0) -⚠️ **There is a known bug** where using mapped enum values with Prisma Client operations causes runtime errors. The TypeScript types expect mapped values, but the engine expects schema names. Track this at [GitHub #28591](https://github.com/prisma/prisma/issues/28591). +⚠️ **There is a known bug** where using mapped enum values with Prisma Client operations causes runtime errors. The TypeScript types expect mapped values, but the engine expects schema names. Track this at [GitHub #28591](https://github.com/prisma/orm/issues/28591). ### Temporary Workarounds diff --git a/apps/docs/content/docs/ai/tools/skills.mdx b/apps/docs/content/docs/ai/tools/skills.mdx index 3800febc29..38cf46e266 100644 --- a/apps/docs/content/docs/ai/tools/skills.mdx +++ b/apps/docs/content/docs/ai/tools/skills.mdx @@ -16,7 +16,7 @@ Prisma ships skills from three repositories, matched to what you are building: | You are working with | Skills repository | Install command | | --- | --- | --- | | Prisma ORM v7, Prisma Postgres, Prisma Compute | [prisma/skills](https://github.com/prisma/skills) | `npx skills add prisma/skills` | -| [Prisma 8](/orm) | [prisma/prisma](https://github.com/prisma/prisma) (`skills/`) | `npx skills add prisma/prisma/skills` | +| [Prisma 8](/orm) | [prisma/prisma](https://github.com/prisma/orm) (`skills/`) | `npx skills add prisma/prisma/skills` | | [Prisma Composer](/composer) | [prisma/composer](https://github.com/prisma/composer) (`skills/`) | `npx skills add prisma/composer` | ## Install @@ -99,7 +99,7 @@ Covers `SqlDriverAdapter`, `Transaction`, savepoint hooks, argument and result m ## Available skills for Prisma 8 -[Prisma 8](/orm) ships its own skills from the [prisma/prisma](https://github.com/prisma/prisma) repository, versioned with the product. Projects scaffolded with `create-prisma` or [`orm init`](/cli/orm-init) install them automatically for every agent runtime the installer supports (Claude Code, Cursor, Codex, Windsurf); skip that step with `orm init --skip-skills`. Add them to an existing project with: +[Prisma 8](/orm) ships its own skills from the [prisma/prisma](https://github.com/prisma/orm) repository, versioned with the product. Projects scaffolded with `create-prisma` or [`orm init`](/cli/orm-init) install them automatically for every agent runtime the installer supports (Claude Code, Cursor, Codex, Windsurf); skip that step with `orm init --skip-skills`. Add them to an existing project with: ```npm npx skills add prisma/prisma/skills diff --git a/apps/docs/content/docs/composer/core-concepts.mdx b/apps/docs/content/docs/composer/core-concepts.mdx index 2396c2a2c4..b5bb5e370e 100644 --- a/apps/docs/content/docs/composer/core-concepts.mdx +++ b/apps/docs/content/docs/composer/core-concepts.mdx @@ -94,7 +94,7 @@ The split is what makes environments cheap: production, a staging stage, a local A **contract** is the typed interface through which services communicate. You write it once as a set of method signatures with Standard Schema message types (arktype, zod, and valibot all work), then both sides use it: the providing service serves it, and a consuming service declares `rpc(contract)` as a dependency and gets a typed client from `service.load()`. On the wire, calls are RPC over HTTP, authenticated with per-consumer service keys Composer provisions for you, and retried safely. See [Services and contracts](/composer/services-and-contracts). -Databases have a contract story of their own: a `pnPostgres()` resource is typed by a [Prisma 8 data contract](/orm/contract-authoring/the-data-contract), and its migrations run as part of the deploy. Every database belongs to exactly one Module, which is what makes migration ownership unambiguous: the Module that owns the database owns its schema. See [Databases](/composer/databases). +Databases have a contract story of their own: a `postgres()` resource is typed by a [Prisma 8 data contract](/orm/contract-authoring/the-data-contract), and its migrations run as part of the deploy. Every database belongs to exactly one Module, which is what makes migration ownership unambiguous: the Module that owns the database owns its schema. See [Databases](/composer/databases). ## The deploy model diff --git a/apps/docs/content/docs/composer/databases.mdx b/apps/docs/content/docs/composer/databases.mdx index be6688928e..ac3017ce9a 100644 --- a/apps/docs/content/docs/composer/databases.mdx +++ b/apps/docs/content/docs/composer/databases.mdx @@ -3,27 +3,27 @@ title: Databases description: Give a service a Postgres database, either as a plain connection or typed by a Prisma 8 contract with managed migrations. url: /composer/databases metaTitle: Databases | Prisma Composer -metaDescription: Add Prisma Postgres to a Composer service with postgres() for a plain connection, or pnPostgres() for a Prisma 8-typed client with deploy-time migrations. +metaDescription: Add Prisma Postgres to a Composer service with rawPostgres() for a plain connection, or postgres() for a Prisma 8-typed client with deploy-time migrations. --- There are two ways for a service to get a [Prisma Postgres](/postgres) database, depending on how much you want the framework to do. Both are dependencies: the service declares the need, the module provisions the resource, and your code receives the result from `service.load()`. :::note[Two kinds of contract] -Composer's [service contracts](/composer/services-and-contracts) describe an RPC API between services. A Prisma 8 **data contract** describes a database schema. This page uses both: `pnPostgres()` ties a database dependency to a Prisma 8 data contract. +Composer's [service contracts](/composer/services-and-contracts) describe an RPC API between services. A Prisma 8 **data contract** describes a database schema. This page uses both: `postgres()` ties a database dependency to a Prisma 8 data contract. ::: -## `postgres()`: bring your own client +## `rawPostgres()`: bring your own client -Declare `postgres()` when you want to build the client yourself. The dependency delivers connection config, `{ url }`, and nothing else. In your server entry, build the client you already know (`pg`, Bun's `SQL`, an ORM): +Declare `rawPostgres()` when you want to build the client yourself. The dependency delivers connection config, `{ url }`, and nothing else. In your server entry, build the client you already know (`pg`, Bun's `SQL`, an ORM): ```ts title="src/auth/service.ts" -import { compute, postgres } from '@prisma/composer-prisma-cloud'; +import { compute, rawPostgres } from '@prisma/composer-prisma-cloud'; export default compute({ name: 'auth', - deps: { db: postgres() }, + deps: { db: rawPostgres() }, // ... }); ``` @@ -40,11 +40,11 @@ Those pool settings matter. Prisma Compute scales to zero and closes idle connec The module that owns the database provisions it: ```ts title="module.ts" -const db = provision(postgres({ name: 'database' })); +const db = provision(rawPostgres({ name: 'database' })); provision(authService, { deps: { db } }); ``` -## `pnPostgres()`: a Prisma 8-typed database +## `postgres()`: a Prisma 8-typed database If you want typed queries and managed migrations, make the database a [Prisma 8](/prisma-orm) one. `load()` then returns `{ url, client }`: the raw connection string, plus a client generated from your data contract. Queries like `db.client.orm.public.Product.where({ id }).first()` are compile-time checked, with no SQL strings and no row mapping. The client is constructed only on first access, so a service that brings its own Postgres client can still read `db.url` and keep contract-checked wiring and deploy-time migrations. @@ -58,30 +58,30 @@ The schema workflow runs once per schema change, using the [Prisma 8 CLI command In your app, wrap the emitted contract once. Both the resource and every service that queries it reference that one value: ```ts title="src/data.ts" -import { pnContract } from '@prisma/composer-prisma-cloud/prisma-next'; +import { dataContract } from '@prisma/composer-prisma-cloud/orm'; import type { Contract } from '../contract.d.ts'; import contractJson from '../contract.json' with { type: 'json' }; -export const catalogData = pnContract(contractJson); +export const catalogData = dataContract(contractJson); ``` -You call `pnPostgres()` on both sides of the wiring, and what you pass it tells the two apart. Passing the contract alone declares the dependency, the service saying what it queries: +You call `postgres()` on both sides of the wiring, and what you pass it tells the two apart. Passing the contract alone declares the dependency, the service saying what it queries: ```ts -deps: { db: pnPostgres(catalogData) } +deps: { db: postgres(catalogData) } ``` Passing an options object declares the resource. The module that owns the database provisions it, naming the `prisma.config.ts` path (relative to the module file) so the deploy can find `migrations/`: ```ts const db = provision( - pnPostgres({ name: 'database', contract: catalogData, config: './prisma.config.ts' }), + postgres({ name: 'database', contract: catalogData, config: './prisma.config.ts' }), ); ``` Because both ends share the contract value, the deploy refuses to wire a service against a database whose schema does not match. -For complete working versions, see [`examples/pn-widgets`](https://github.com/prisma/composer/tree/main/examples/pn-widgets) (one service, one typed database) and [`examples/store`](https://github.com/prisma/composer/tree/main/examples/store) (the full pattern inside a reusable Module) in the Composer repository. +For complete working versions, see [`examples/orm-demo`](https://github.com/prisma/composer/tree/main/examples/orm-demo) (one service, one typed database) and [`examples/store`](https://github.com/prisma/composer/tree/main/examples/store) (the full pattern inside a reusable Module) in the Composer repository. ## Local databases diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx index 8a98578899..67add47c14 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx @@ -367,6 +367,6 @@ This tool helps with: ## Getting Help If you encounter issues during migration: -1. Search the [GitHub Issues](https://github.com/prisma/prisma/issues) +1. Search the [GitHub Issues](https://github.com/prisma/orm/issues) 2. Ask for help in the [Prisma Slack](https://slack.prisma.io/) -3. Open a [GitHub Discussion](https://github.com/prisma/prisma/discussions) +3. Open a [GitHub Discussion](https://github.com/prisma/orm/discussions) diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v3.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v3.mdx index 1072bfbf71..74cc063487 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v3.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v3.mdx @@ -12,7 +12,7 @@ This guide helps you upgrade your project to Prisma ORM v3. Version 3 includes s ## Before you begin - **Backup your database** before starting the upgrade process -- Review the [release notes](https://github.com/prisma/prisma/releases/tag/3.0.1) for a complete list of changes +- Review the [release notes](https://github.com/prisma/orm/releases/tag/3.0.1) for a complete list of changes - Test the upgrade in a development or staging environment first ## Key changes @@ -256,7 +256,7 @@ Before you upgrade, check each breaking change below to see how the upgrade migh ## Next Steps -- [Prisma ORM 3 Release Notes](https://github.com/prisma/prisma/releases/tag/3.0.1) +- [Prisma ORM 3 Release Notes](https://github.com/prisma/orm/releases/tag/3.0.1) - [Prisma Schema Reference](/orm/v7/reference/prisma-schema-reference) - [Prisma Client API Reference](/orm/v7/reference/prisma-client-reference) - [Raw Database Access](/orm/v7/prisma-client/using-raw-sql/raw-queries) diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v4.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v4.mdx index 9fcb51338c..98a3a8a7a0 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v4.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v4.mdx @@ -12,7 +12,7 @@ This guide helps you upgrade your project to Prisma ORM 4. Version 4 includes se ## Before you begin - **Back up your database** before starting the upgrade -- Review the [release notes](https://github.com/prisma/prisma/releases/tag/4.0.0) for a complete list of changes +- Review the [release notes](https://github.com/prisma/orm/releases/tag/4.0.0) for a complete list of changes - Test the upgrade in a development or staging environment first - Ensure you're using Node.js 14.17.0 or later (required for Prisma 4+) @@ -280,7 +280,7 @@ Prisma 4 improves type safety with: ## Next Steps -- [Prisma 4.0.0 Release Notes](https://github.com/prisma/prisma/releases/tag/4.0.0) +- [Prisma 4.0.0 Release Notes](https://github.com/prisma/orm/releases/tag/4.0.0) - [Prisma Schema Reference](/orm/v7/reference/prisma-schema-reference) - [Prisma Client API Reference](/orm/v7/reference/prisma-client-reference) - [Raw Database Access](/orm/v7/prisma-client/using-raw-sql/raw-queries) @@ -288,6 +288,6 @@ Prisma 4 improves type safety with: ## Getting Help If you encounter issues during the upgrade: -1. Check the [GitHub Issues](https://github.com/prisma/prisma/issues) for known problems +1. Check the [GitHub Issues](https://github.com/prisma/orm/issues) for known problems 2. Ask for help in the [Prisma Slack](https://slack.prisma.io/) -3. Open a [GitHub Discussion](https://github.com/prisma/prisma/discussions) +3. Open a [GitHub Discussion](https://github.com/prisma/orm/discussions) diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v5.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v5.mdx index 17ee04d5c2..8b31ff7e30 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v5.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v5.mdx @@ -7,7 +7,7 @@ metaDescription: 'Guides on how to upgrade to Prisma ORM 5' --- -Prisma ORM v5.0.0 introduces a number of changes, including the usage of our new JSON Protocol, [which makes Prisma Client faster by default](https://www.prisma.io/blog/prisma-5-f66prwkjx72s). A full list of these changes can be found [in our release notes](https://github.com/prisma/prisma/releases/tag/5.0.0). +Prisma ORM v5.0.0 introduces a number of changes, including the usage of our new JSON Protocol, [which makes Prisma Client faster by default](https://www.prisma.io/blog/prisma-5-f66prwkjx72s). A full list of these changes can be found [in our release notes](https://github.com/prisma/orm/releases/tag/5.0.0). This guide explains how upgrading might affect your application and gives instructions on how to handle breaking changes within Prisma ORM 5. diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v7.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v7.mdx index 7b34c1ae1e..92eae47c97 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v7.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v7.mdx @@ -286,7 +286,7 @@ export default defineConfig({ ### Metrics removed -The Metrics preview feature was deprecated in [Prisma ORM 6.14.0](https://github.com/prisma/prisma/releases/tag/6.14.0) and has been removed for Prisma ORM 7.0.0. +The Metrics preview feature was deprecated in [Prisma ORM 6.14.0](https://github.com/prisma/orm/releases/tag/6.14.0) and has been removed for Prisma ORM 7.0.0. If you need this feature, you can use the underlying driver adapter for your database, or Client Extensions to make this information available. For example, a basic `totalQueries` counter: diff --git a/apps/docs/content/docs/orm/extensions/using-extensions.mdx b/apps/docs/content/docs/orm/extensions/using-extensions.mdx index 9c8e06d305..c68afad544 100644 --- a/apps/docs/content/docs/orm/extensions/using-extensions.mdx +++ b/apps/docs/content/docs/orm/extensions/using-extensions.mdx @@ -107,15 +107,15 @@ You can build an extension that does not exist yet. The catalog is first-party t | Extension | Adds | Package | | --- | --- | --- | -| [pgvector](https://github.com/prisma/prisma/tree/main/packages/3-extensions/pgvector#readme) | Vector columns and similarity search | `@prisma/orm-extension-pgvector` | -| [PostGIS](https://github.com/prisma/prisma/tree/main/packages/3-extensions/postgis#readme) | Geometry columns and geo queries | `@prisma/orm-extension-postgis` | -| [ParadeDB](https://github.com/prisma/prisma/tree/main/packages/3-extensions/paradedb#readme) | BM25 full-text search indexes | `@prisma/orm-extension-paradedb` | -| [Supabase](https://github.com/prisma/prisma/tree/main/packages/3-extensions/supabase#readme) | Supabase auth and storage tables, role-bound clients | `@prisma/orm-extension-supabase` | -| [arktype-json](https://github.com/prisma/prisma/tree/main/packages/3-extensions/arktype-json#readme) | JSON columns validated by an arktype schema | `@prisma/orm-extension-arktype-json` | +| [pgvector](https://github.com/prisma/orm/tree/main/packages/3-extensions/pgvector#readme) | Vector columns and similarity search | `@prisma/orm-extension-pgvector` | +| [PostGIS](https://github.com/prisma/orm/tree/main/packages/3-extensions/postgis#readme) | Geometry columns and geo queries | `@prisma/orm-extension-postgis` | +| [ParadeDB](https://github.com/prisma/orm/tree/main/packages/3-extensions/paradedb#readme) | BM25 full-text search indexes | `@prisma/orm-extension-paradedb` | +| [Supabase](https://github.com/prisma/orm/tree/main/packages/3-extensions/supabase#readme) | Supabase auth and storage tables, role-bound clients | `@prisma/orm-extension-supabase` | +| [arktype-json](https://github.com/prisma/orm/tree/main/packages/3-extensions/arktype-json#readme) | JSON columns validated by an arktype schema | `@prisma/orm-extension-arktype-json` | All target PostgreSQL. ParadeDB and Supabase are experimental (ParadeDB supports the `key_field` index option only so far). The rest ship with Prisma 8. Extension names link to each package's README on GitHub. -For a working project per extension, see the runnable examples: [pgvector](https://github.com/prisma/prisma/tree/main/examples/prisma-8-demo), [PostGIS](https://github.com/prisma/prisma/tree/main/examples/prisma-8-postgis-demo), [ParadeDB](https://github.com/prisma/prisma/tree/main/examples/paradedb-demo), and [Supabase](https://github.com/prisma/prisma/tree/main/examples/supabase). +For a working project per extension, see the runnable examples: [pgvector](https://github.com/prisma/orm/tree/main/examples/prisma-8-demo), [PostGIS](https://github.com/prisma/orm/tree/main/examples/prisma-8-postgis-demo), [ParadeDB](https://github.com/prisma/orm/tree/main/examples/paradedb-demo), and [Supabase](https://github.com/prisma/orm/tree/main/examples/supabase). ## See also diff --git a/apps/docs/content/docs/orm/index.mdx b/apps/docs/content/docs/orm/index.mdx index f12817a782..656a68ea7f 100644 --- a/apps/docs/content/docs/orm/index.mdx +++ b/apps/docs/content/docs/orm/index.mdx @@ -107,4 +107,4 @@ The thinking behind Prisma 8 is documented on the [Prisma blog](https://www.pris - **[Rethinking Database Migrations](https://www.prisma.io/blog/rethinking-database-migrations)**: how graph-based migrations replace timestamp ordering with schema state hashes. - **[Prisma 8 Is ~90% As Fast as Raw PG](https://www.prisma.io/blog/prisma-next-performance-benchmark)**: benchmarks against the raw PostgreSQL driver. -The full series also covers [TypeScript migrations](https://www.prisma.io/blog/typescript-migrations-in-prisma-next), [data migrations](https://www.prisma.io/blog/data-migrations-in-prisma-next), [the extension API](https://www.prisma.io/blog/prisma-next-call-for-extension-authors), the [roadmap](https://www.prisma.io/blog/prisma-next-roadmap), and the [early-access launch](https://www.prisma.io/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app). The source lives on [GitHub](https://github.com/prisma/prisma). +The full series also covers [TypeScript migrations](https://www.prisma.io/blog/typescript-migrations-in-prisma-next), [data migrations](https://www.prisma.io/blog/data-migrations-in-prisma-next), [the extension API](https://www.prisma.io/blog/prisma-next-call-for-extension-authors), the [roadmap](https://www.prisma.io/blog/prisma-next-roadmap), and the [early-access launch](https://www.prisma.io/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app). The source lives on [GitHub](https://github.com/prisma/orm). diff --git a/apps/docs/content/docs/orm/migrations/editing-a-migration.mdx b/apps/docs/content/docs/orm/migrations/editing-a-migration.mdx index 37326493b8..840299e67b 100644 --- a/apps/docs/content/docs/orm/migrations/editing-a-migration.mdx +++ b/apps/docs/content/docs/orm/migrations/editing-a-migration.mdx @@ -194,7 +194,7 @@ override get operations() { } ``` -The full working migration, including the two query-plan helpers, is in the Prisma 8 repo's [retail-store example](https://github.com/prisma/prisma/blob/main/examples/retail-store/migrations/app/20260513T0508_backfill_product_status/migration.ts). +The full working migration, including the two query-plan helpers, is in the Prisma 8 repo's [retail-store example](https://github.com/prisma/orm/blob/main/examples/retail-store/migrations/app/20260513T0508_backfill_product_status/migration.ts). ## Starting from a blank migration diff --git a/apps/docs/content/docs/orm/migrations/the-migration-graph.mdx b/apps/docs/content/docs/orm/migrations/the-migration-graph.mdx index 7947dcd1d4..64b8f55fc9 100644 --- a/apps/docs/content/docs/orm/migrations/the-migration-graph.mdx +++ b/apps/docs/content/docs/orm/migrations/the-migration-graph.mdx @@ -114,7 +114,7 @@ Four read-only commands, each answering a different question: The Prisma 8 repo ships example graphs (a diamond, a wide fan-out, converging branches, rollback chains) as ready-to-render fixtures: ```bash -git clone https://github.com/prisma/prisma +git clone https://github.com/prisma/orm cd prisma && pnpm install && pnpm -w build && pnpm install cd examples/prisma-8-demo npx prisma@latest migration graph --config fixtures/showcase/prisma.config.ts --legend diff --git a/apps/docs/content/docs/orm/reference/error-reference.mdx b/apps/docs/content/docs/orm/reference/error-reference.mdx index 321c367d69..b554b0b08d 100644 --- a/apps/docs/content/docs/orm/reference/error-reference.mdx +++ b/apps/docs/content/docs/orm/reference/error-reference.mdx @@ -7,10 +7,10 @@ metaDescription: Every structured error code Prisma 8 can emit, by namespace, wi --- {/* Generated by scripts/generate-error-reference.mjs from - https://github.com/prisma/prisma/blob/main/docs/reference/error-reference.md + https://github.com/prisma/orm/blob/main/docs/reference/error-reference.md Do not edit by hand — changes are overwritten by the sync workflow. */} -Every user-facing Prisma 8 error is a structured envelope identified by a dotted `NAMESPACE.SUBCODE` code (see [ADR 239](https://github.com/prisma/prisma/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md) and [Error Handling](https://github.com/prisma/prisma/blob/main/docs/Error%20Handling.md)). This page lists every published code. Each code anchors as `#` — the exact fragment every emitted error carries in its `docsUrl`. This page is generated from the canonical reference in the `prisma/prisma` repository, whose CI requires every code in production source to be documented before it ships. +Every user-facing Prisma 8 error is a structured envelope identified by a dotted `NAMESPACE.SUBCODE` code (see [ADR 239](https://github.com/prisma/orm/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md) and [Error Handling](https://github.com/prisma/orm/blob/main/docs/Error%20Handling.md)). This page lists every published code. Each code anchors as `#` — the exact fragment every emitted error carries in its `docsUrl`. This page is generated from the canonical reference in the `prisma/prisma` repository, whose CI requires every code in production source to be documented before it ships. Recognize an error programmatically with `isStructuredError` from your facade package's `utils/structured-error` subpath (for example `@prisma/orm-postgres/utils/structured-error`) and match on `error.code` — never `instanceof`. Envelopes carry `message`, and optionally `why`, `fix`, `where`, `meta`, `cause`, and `docsUrl`. @@ -20,7 +20,7 @@ Some codes are not failures to run at all. `db verify`, `db sign` and `migration A command may also **complete with findings**: it ran to its end and has a result to report, and the problems it found ride that result as diagnostics carrying the codes on this page. Those runs exit with a documented per-command code in the `4`–`99` band rather than `2`, and the entry below says so. `prisma orm init` is the case today: its scaffold is on disk whatever happens next, so a failed dependency install or contract emit is a finding on a completed run at exit `4` or `5`. -Codes that predate the dotted scheme were renamed at 0.16; the full old→new crosswalk (`PN-DOMAIN-NNNN` → `NAMESPACE.SUBCODE`) is in [ADR 239](https://github.com/prisma/prisma/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md). +Codes that predate the dotted scheme were renamed at 0.16; the full old→new crosswalk (`PN-DOMAIN-NNNN` → `NAMESPACE.SUBCODE`) is in [ADR 239](https://github.com/prisma/orm/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md). Namespaces: @@ -195,7 +195,7 @@ A `package.json` found while resolving the project import root exists but could ### CLI.PROMPT_REQUIRED [#CLI.PROMPT_REQUIRED] -Raised by `@prisma/cli-engine`, not by this repository: a command asked a question that has no default, and the session could not show it — stdin is not a terminal, `--no-interactive` was passed, or `--yes` was asked to answer a prompt that declares no default. The `CLI` namespace is shared with the engine (see [ADR 239](https://github.com/prisma/prisma/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md)); it is listed here because it settles runs of the ORM's commands. `prisma orm init` translates it for the two prompts that stand in for a required flag, so a missing `--target` or `--authoring` still reports `CLI.INIT_MISSING_FLAGS` with the full missing list. Meta: none. +Raised by `@prisma/cli-engine`, not by this repository: a command asked a question that has no default, and the session could not show it — stdin is not a terminal, `--no-interactive` was passed, or `--yes` was asked to answer a prompt that declares no default. The `CLI` namespace is shared with the engine (see [ADR 239](https://github.com/prisma/orm/blob/main/docs/architecture%20docs/adrs/ADR%20239%20-%20Errors%20are%20structural%20envelopes%20with%20dotted%20namespace%20codes.md)); it is listed here because it settles runs of the ORM's commands. `prisma orm init` translates it for the two prompts that stand in for a required flag, so a missing `--target` or `--authoring` still reports `CLI.INIT_MISSING_FLAGS` with the full missing list. Meta: none. ### CLI.UNEXPECTED [#CLI.UNEXPECTED] @@ -745,7 +745,7 @@ Executing a prepared statement without supplying a value for one of its declared ### RUNTIME.RAW_ROW_COLUMN_MISSING [#RUNTIME.RAW_ROW_COLUMN_MISSING] -A whole-query raw statement returned a result that omits a column its row spec declares. The runtime never parses the SQL, so the spec is its only description of the result — a column the spec names and the statement does not return is a mismatch the caller has to resolve, by correcting the spec or the statement. Distinct from `RUNTIME.DECODE_FAILED`, which means a codec rejected a value the runtime did expect. Surplus result columns the spec does not declare are dropped silently and never raise this. See [ADR 247](https://github.com/prisma/prisma/blob/main/docs/architecture%20docs/adrs/ADR%20247%20-%20Whole-query%20raw%20SQL%20is%20the%20fragment%20mechanism%20at%20statement%20position.md). Meta: `column`, `declaredColumns`, `resultColumns`. +A whole-query raw statement returned a result that omits a column its row spec declares. The runtime never parses the SQL, so the spec is its only description of the result — a column the spec names and the statement does not return is a mismatch the caller has to resolve, by correcting the spec or the statement. Distinct from `RUNTIME.DECODE_FAILED`, which means a codec rejected a value the runtime did expect. Surplus result columns the spec does not declare are dropped silently and never raise this. See [ADR 247](https://github.com/prisma/orm/blob/main/docs/architecture%20docs/adrs/ADR%20247%20-%20Whole-query%20raw%20SQL%20is%20the%20fragment%20mechanism%20at%20statement%20position.md). Meta: `column`, `declaredColumns`, `resultColumns`. ### RUNTIME.RAW_SQL_UNSUPPORTED_INTERPOLATION [#RUNTIME.RAW_SQL_UNSUPPORTED_INTERPOLATION] diff --git a/apps/docs/content/docs/orm/v6/index.mdx b/apps/docs/content/docs/orm/v6/index.mdx index 96b243056e..fc408c1527 100644 --- a/apps/docs/content/docs/orm/v6/index.mdx +++ b/apps/docs/content/docs/orm/v6/index.mdx @@ -6,7 +6,7 @@ metaTitle: ORM metaDescription: ORM --- -[Prisma ORM](https://github.com/prisma/prisma) is a Node.js and TypeScript ORM with an intuitive data model, automated migrations, type-safety, and auto-completion. +[Prisma ORM](https://github.com/prisma/orm) is a Node.js and TypeScript ORM with an intuitive data model, automated migrations, type-safety, and auto-completion. ## Getting started diff --git a/apps/docs/content/docs/orm/v6/more/internals/engines.mdx b/apps/docs/content/docs/orm/v6/more/internals/engines.mdx index 6eb80f14b5..73e3634c01 100644 --- a/apps/docs/content/docs/orm/v6/more/internals/engines.mdx +++ b/apps/docs/content/docs/orm/v6/more/internals/engines.mdx @@ -88,9 +88,9 @@ Use the following environment variables to specify custom locations for your Rus **Earlier deprecations:** -- `PRISMA_MIGRATION_ENGINE_BINARY` variable is deprecated in [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) because the Migration engine was renamed to Schema Engine. -- The Introspection Engine is served by the Schema Engine from [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used. -- The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/prisma/prisma/releases/tag/4.2.0) or lower. +- `PRISMA_MIGRATION_ENGINE_BINARY` variable is deprecated in [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) because the Migration engine was renamed to Schema Engine. +- The Introspection Engine is served by the Schema Engine from [4.9.0](https://github.com/prisma/orm/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used. +- The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/prisma/orm/releases/tag/4.2.0) or lower. ::: @@ -284,7 +284,7 @@ The environment variable `PRISMA_CLIENT_ENGINE_TYPE` is not supported in Prisma :::info[Historical context] - Until Prisma 3.x the default and only engine type available was `binary`, so there was no way to configure the engine type to be used by Prisma Client and Prisma CLI. -- From versions [2.20.0](https://github.com/prisma/prisma/releases/2.20.0) to 3.x the `library` engine type was available and used by default by [activating the preview feature flag](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) "`nApi`" or using the `PRISMA_FORCE_NAPI=true` environment variable. +- From versions [2.20.0](https://github.com/prisma/orm/releases/2.20.0) to 3.x the `library` engine type was available and used by default by [activating the preview feature flag](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) "`nApi`" or using the `PRISMA_FORCE_NAPI=true` environment variable. - As of Prisma ORM v7, the TypeScript-based query compiler (no Rust binaries) is the default and `engineType` does not need to be set. ::: diff --git a/apps/docs/content/docs/orm/v6/more/releases.mdx b/apps/docs/content/docs/orm/v6/more/releases.mdx index e405c09023..06777edd82 100644 --- a/apps/docs/content/docs/orm/v6/more/releases.mdx +++ b/apps/docs/content/docs/orm/v6/more/releases.mdx @@ -12,13 +12,13 @@ This page explains the release process of Prisma ORM, how it's versioned and how Prisma ORM releases typically happen every two weeks. Note that this is _not_ a hard rule – releases might be postponed for internal reasons. -[Check out all the releases notes in GitHub](https://github.com/prisma/prisma/releases). +[Check out all the releases notes in GitHub](https://github.com/prisma/orm/releases). ## Product maturity levels A release can include products or features at different maturity levels. Maturity level describes a product or feature's completeness and what users can expect in terms of breaking changes. -> **Note**: As of version [2.13.0](https://github.com/prisma/prisma/releases/2.13.0), 'Experimental' is no longer part of the product maturity scale. +> **Note**: As of version [2.13.0](https://github.com/prisma/orm/releases/2.13.0), 'Experimental' is no longer part of the product maturity scale. ### Early Access diff --git a/apps/docs/content/docs/orm/v6/more/troubleshooting/bundler-issues.mdx b/apps/docs/content/docs/orm/v6/more/troubleshooting/bundler-issues.mdx index fb684f36dd..468ab349f6 100644 --- a/apps/docs/content/docs/orm/v6/more/troubleshooting/bundler-issues.mdx +++ b/apps/docs/content/docs/orm/v6/more/troubleshooting/bundler-issues.mdx @@ -26,4 +26,4 @@ Add your Prisma query engine binary path to the `pkg/assets` section of your `pa } ``` -See [this Github issue](https://github.com/prisma/prisma/issues/8449) for further discussion. +See [this Github issue](https://github.com/prisma/orm/issues/8449) for further discussion. diff --git a/apps/docs/content/docs/orm/v6/more/upgrades/from-v1.mdx b/apps/docs/content/docs/orm/v6/more/upgrades/from-v1.mdx index ecab7968b5..3bd880b395 100644 --- a/apps/docs/content/docs/orm/v6/more/upgrades/from-v1.mdx +++ b/apps/docs/content/docs/orm/v6/more/upgrades/from-v1.mdx @@ -101,4 +101,4 @@ If you encounter issues during migration: 1. Check the [Prisma 1 Upgrade CLI repository](https://github.com/prisma/prisma1-upgrade) for known issues 2. Visit the [Prisma Discord](https://pris.ly/discord) for community support -3. Open an issue on [GitHub](https://github.com/prisma/prisma/issues) for bugs +3. Open an issue on [GitHub](https://github.com/prisma/orm/issues) for bugs diff --git a/apps/docs/content/docs/orm/v6/more/upgrades/to-v7.mdx b/apps/docs/content/docs/orm/v6/more/upgrades/to-v7.mdx index 6da593762d..14d0e36129 100644 --- a/apps/docs/content/docs/orm/v6/more/upgrades/to-v7.mdx +++ b/apps/docs/content/docs/orm/v6/more/upgrades/to-v7.mdx @@ -245,7 +245,7 @@ const adapter = new PrismaPg({ Or properly configure your database certificates using `node --use-openssl-ca` or by setting the `NODE_EXTRA_CA_CERTS` environment variable. -For more details, see [GitHub issue #28795](https://github.com/prisma/prisma/issues/28795). +For more details, see [GitHub issue #28795](https://github.com/prisma/orm/issues/28795). ### Explicit loading of environment variables @@ -302,7 +302,7 @@ export default defineConfig({ ### Metrics has been removed from the Client extensions -The Metrics preview feature was deprecated in [Prisma ORM 6.14.0](https://github.com/prisma/prisma/releases/tag/6.14.0) and has been removed for Prisma ORM 7.0.0. +The Metrics preview feature was deprecated in [Prisma ORM 6.14.0](https://github.com/prisma/orm/releases/tag/6.14.0) and has been removed for Prisma ORM 7.0.0. If you need this feature, you can use the underlying driver adapter for your database, or Client Extensions to make this information available. For example, a basic `totalQueries` counter: diff --git a/apps/docs/content/docs/orm/v6/overview/databases/cloudflare-d1.mdx b/apps/docs/content/docs/orm/v6/overview/databases/cloudflare-d1.mdx index 8a862ea2c8..d2c40adb9f 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/cloudflare-d1.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/cloudflare-d1.mdx @@ -9,7 +9,7 @@ metaDescription: Guide to Cloudflare D1 This page discusses the concepts behind using Prisma ORM and Cloudflare D1, explains the commonalities and differences between Cloudflare D1 and other database providers, and leads you through the process for configuring your application to integrate with Cloudflare D1. -Prisma ORM support for Cloudflare D1 is currently in [Preview](/orm/v6/more/releases#preview). We would appreciate your feedback [on GitHub](https://github.com/prisma/prisma/discussions/23646). +Prisma ORM support for Cloudflare D1 is currently in [Preview](/orm/v6/more/releases#preview). We would appreciate your feedback [on GitHub](https://github.com/prisma/orm/discussions/23646). If you want to deploy a Cloudflare Worker with D1 and Prisma ORM, follow this [tutorial](/guides/deployment/cloudflare-d1). diff --git a/apps/docs/content/docs/orm/v6/overview/databases/cockroachdb.mdx b/apps/docs/content/docs/orm/v6/overview/databases/cockroachdb.mdx index c7a9bf1eec..3caf1df2a8 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/cockroachdb.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/cockroachdb.mdx @@ -10,7 +10,7 @@ This guide discusses the concepts behind using Prisma ORM and CockroachDB, expla :::info -The CockroachDB connector is generally available in versions `3.14.0` and later. It was first added as a [Preview feature](/orm/v6/reference/preview-features) in version [`3.9.0`](https://github.com/prisma/prisma/releases/tag/3.9.0) with support for Introspection, and Prisma Migrate support was added in [`3.11.0`](https://github.com/prisma/prisma/releases/tag/3.11.0). +The CockroachDB connector is generally available in versions `3.14.0` and later. It was first added as a [Preview feature](/orm/v6/reference/preview-features) in version [`3.9.0`](https://github.com/prisma/orm/releases/tag/3.9.0) with support for Introspection, and Prisma Migrate support was added in [`3.11.0`](https://github.com/prisma/orm/releases/tag/3.11.0). ::: diff --git a/apps/docs/content/docs/orm/v6/overview/databases/database-drivers.mdx b/apps/docs/content/docs/orm/v6/overview/databases/database-drivers.mdx index 39e0aaa2f3..5667fb5679 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/database-drivers.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/database-drivers.mdx @@ -97,7 +97,7 @@ Refer to the following pages to learn more about how to use the specific driver ### New driver adapters API in v6.6.0 -In [v6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0), we introduced a simplified version for instantiating Prisma Client when using driver adapters. You now don't need to create an instance of the driver/client to pass to a driver adapter, instead you can create the driver adapter directly (and pass the driver's options to it if needed). +In [v6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0), we introduced a simplified version for instantiating Prisma Client when using driver adapters. You now don't need to create an instance of the driver/client to pass to a driver adapter, instead you can create the driver adapter directly (and pass the driver's options to it if needed). Here is an example using the `@prisma/adapter-libsql` adapter: diff --git a/apps/docs/content/docs/orm/v6/overview/databases/mysql.mdx b/apps/docs/content/docs/orm/v6/overview/databases/mysql.mdx index 142a24eda3..0ab57282b7 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/mysql.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/mysql.mdx @@ -40,7 +40,7 @@ This configuration uses an [environment variable](/orm/v6/prisma-schema/overview ## Using the `mariadb` driver -As of [`v5.4.0`](https://github.com/prisma/prisma/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). +As of [`v5.4.0`](https://github.com/prisma/orm/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). For MySQL and MariaDB, [`mariadb`](https://github.com/mariadb-corporation/mariadb-connector-nodejs) is one of the most popular drivers in the JavaScript ecosystem. diff --git a/apps/docs/content/docs/orm/v6/overview/databases/planetscale.mdx b/apps/docs/content/docs/orm/v6/overview/databases/planetscale.mdx index 81484b26af..b1f6a13815 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/planetscale.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/planetscale.mdx @@ -256,7 +256,7 @@ For a more detailed example, see the [Getting started guide for PlanetScale](/v7 [Sharding](https://planetscale.com/docs/vitess/sharding) is a popular technique to scale up when database load grows. -As of [v6.10.0](https://github.com/prisma/prisma/releases/tag/6.10.0), Prisma ORM supports sharding on PlanetScale natively (as a [Preview](/orm/v6/more/releases#preview) feature) via the [`@shardKey`](/orm/v6/reference/prisma-schema-reference#shardkey) and [`@@shardKey`](/orm/v6/reference/prisma-schema-reference#shardkey-1) attributes in the Prisma schema which you can apply to the fields in your models that should serve as shard keys in your database setup. +As of [v6.10.0](https://github.com/prisma/orm/releases/tag/6.10.0), Prisma ORM supports sharding on PlanetScale natively (as a [Preview](/orm/v6/more/releases#preview) feature) via the [`@shardKey`](/orm/v6/reference/prisma-schema-reference#shardkey) and [`@@shardKey`](/orm/v6/reference/prisma-schema-reference#shardkey-1) attributes in the Prisma schema which you can apply to the fields in your models that should serve as shard keys in your database setup. In order to use the shard key attributes, you need to specify the `shardKeys` Preview feature on your `generator`: diff --git a/apps/docs/content/docs/orm/v6/overview/databases/postgresql.mdx b/apps/docs/content/docs/orm/v6/overview/databases/postgresql.mdx index c0fac02986..a8b091a481 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/postgresql.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/postgresql.mdx @@ -48,7 +48,7 @@ This configuration uses an [environment variable](/orm/v6/prisma-schema/overview ## Using the `node-postgres` driver -As of [`v5.4.0`](https://github.com/prisma/prisma/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). +As of [`v5.4.0`](https://github.com/prisma/orm/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). For PostgreSQL, [`node-postgres`](https://node-postgres.com) (`pg`) is one of the most popular drivers in the JavaScript ecosystem. It can be used with any PostgreSQL database that's accessed via TCP. diff --git a/apps/docs/content/docs/orm/v6/overview/databases/sql-server/index.mdx b/apps/docs/content/docs/orm/v6/overview/databases/sql-server/index.mdx index cfdb957d5a..64a8d138de 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/sql-server/index.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/sql-server/index.mdx @@ -45,7 +45,7 @@ The fields passed to the `datasource` block are: ## Using the `node-mssql` driver -As of [`v5.4.0`](https://github.com/prisma/prisma/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). +As of [`v5.4.0`](https://github.com/prisma/orm/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). For SQLite, [`node-mssql`](https://github.com/tediousjs/node-mssql) is one of the most popular drivers in the JavaScript ecosystem. @@ -175,7 +175,7 @@ See [Supported databases](/orm/v6/reference/supported-databases). ### Prisma Migrate caveats -Prisma Migrate is supported in [2.13.0](https://github.com/prisma/prisma/releases/tag/2.13.0) and later with the following caveats: +Prisma Migrate is supported in [2.13.0](https://github.com/prisma/orm/releases/tag/2.13.0) and later with the following caveats: #### Database schema names diff --git a/apps/docs/content/docs/orm/v6/overview/databases/sqlite.mdx b/apps/docs/content/docs/orm/v6/overview/databases/sqlite.mdx index 1a70fbdf66..10c9524adc 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/sqlite.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/sqlite.mdx @@ -39,7 +39,7 @@ The connection URL always starts with the prefix `file:` and then contains a fil ## Using the `better-sqlite3` driver -As of [`v5.4.0`](https://github.com/prisma/prisma/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). +As of [`v5.4.0`](https://github.com/prisma/orm/releases/tag/5.4.0), you can use Prisma ORM with database drivers from the JavaScript ecosystem (instead of using Prisma ORM's built-in drivers). You can do this by using a [driver adapter](/orm/v6/overview/databases/database-drivers). For SQLite, [`better-sqlite3`](https://github.com/WiseLibs/better-sqlite3) is one of the most popular drivers in the JavaScript ecosystem. diff --git a/apps/docs/content/docs/orm/v6/overview/databases/supabase.mdx b/apps/docs/content/docs/orm/v6/overview/databases/supabase.mdx index 8a3113946e..0ce72552e9 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/supabase.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/supabase.mdx @@ -87,4 +87,4 @@ We strongly recommend using connection pooling with Supavisor in addition to `DI Supabase has a guide for connecting a Supabase database to your Prisma project [here](https://supabase.com/partners/integrations/prisma). -If you're running into issues integrating with Supabase, check out these [specific troubleshooting tips](https://supabase.com/partners/integrations/prisma) or [Prisma's GitHub Discussions](https://github.com/prisma/prisma/discussions) for more help. +If you're running into issues integrating with Supabase, check out these [specific troubleshooting tips](https://supabase.com/partners/integrations/prisma) or [Prisma's GitHub Discussions](https://github.com/prisma/orm/discussions) for more help. diff --git a/apps/docs/content/docs/orm/v6/overview/introduction/should-you-use-prisma.mdx b/apps/docs/content/docs/orm/v6/overview/introduction/should-you-use-prisma.mdx index cad2c5627e..5bb2548cd1 100644 --- a/apps/docs/content/docs/orm/v6/overview/introduction/should-you-use-prisma.mdx +++ b/apps/docs/content/docs/orm/v6/overview/introduction/should-you-use-prisma.mdx @@ -61,11 +61,11 @@ In addition to the intuitive, higher-level query API, Prisma ORM also offers a w ### ... you want an ORM with a transparent development process, proper maintenance & support -Development of Prisma ORM's open source tools is happening in the open. Most of it happens directly on GitHub in the main [`prisma/prisma`](https://github.com/prisma/prisma) repo: +Development of Prisma ORM's open source tools is happening in the open. Most of it happens directly on GitHub in the main [`prisma/prisma`](https://github.com/prisma/orm) repo: - issues and PRs in our repos are triaged and prioritized (usually within 1-2 days) -- new [releases](https://github.com/prisma/prisma/releases) with new features and improvements are issued every three weeks -- we have a dedicated support team that responds to questions in [GitHub Discussions](https://github.com/prisma/prisma/discussions) +- new [releases](https://github.com/prisma/orm/releases) with new features and improvements are issued every three weeks +- we have a dedicated support team that responds to questions in [GitHub Discussions](https://github.com/prisma/orm/discussions) ### ... you want an active community diff --git a/apps/docs/content/docs/orm/v6/overview/introduction/what-is-prisma.mdx b/apps/docs/content/docs/orm/v6/overview/introduction/what-is-prisma.mdx index 7dde310d7e..4d531ecccc 100644 --- a/apps/docs/content/docs/orm/v6/overview/introduction/what-is-prisma.mdx +++ b/apps/docs/content/docs/orm/v6/overview/introduction/what-is-prisma.mdx @@ -6,7 +6,7 @@ metaTitle: What is Prisma ORM? (Prisma 6 overview) metaDescription: This page gives a high-level overview of what Prisma ORM is and how it works. It's a great starting point for Prisma newcomers! --- -Prisma ORM is an [open-source](https://github.com/prisma/prisma) next-generation ORM. It consists of the following parts: +Prisma ORM is an [open-source](https://github.com/prisma/orm) next-generation ORM. It consists of the following parts: - **Prisma Client**: Auto-generated and type-safe query builder for Node.js & TypeScript - **Prisma Migrate**: Migration system diff --git a/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/result.mdx b/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/result.mdx index ea3b490ff6..73573f6af7 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/result.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/result.mdx @@ -202,7 +202,7 @@ In this case, omitting both `password` and `sanitizedPassword` will exclude both ## Limitation -As of now, Prisma Client's result extension component does not support relation fields. This means that you cannot create custom fields or methods based on related models or fields in a relational relationship (e.g., user.posts, post.author). The needs parameter can only reference scalar fields within the same model. Follow [issue #20091 on GitHub](https://github.com/prisma/prisma/issues/20091). +As of now, Prisma Client's result extension component does not support relation fields. This means that you cannot create custom fields or methods based on related models or fields in a relational relationship (e.g., user.posts, post.author). The needs parameter can only reference scalar fields within the same model. Follow [issue #20091 on GitHub](https://github.com/prisma/orm/issues/20091). ```ts const prisma = new PrismaClient().$extends({ diff --git a/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/shared-extensions/index.mdx b/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/shared-extensions/index.mdx index 008f815053..04bd8ac965 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/shared-extensions/index.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/client-extensions/shared-extensions/index.mdx @@ -109,7 +109,7 @@ There's currently a limitation for extensions that reference a `PrismaClient` an If you trigger the extension from inside a [transaction](/orm/v6/prisma-client/queries/transactions) (interactive or batched), the extension code will issue the queries in a new connection and ignore the current transaction context. -Learn more in this issue on GitHub: [Client extensions that require use of a client-level method silently ignore transactions](https://github.com/prisma/prisma/issues/20678). +Learn more in this issue on GitHub: [Client extensions that require use of a client-level method silently ignore transactions](https://github.com/prisma/orm/issues/20678). ::: diff --git a/apps/docs/content/docs/orm/v6/prisma-client/observability-and-logging/metrics.mdx b/apps/docs/content/docs/orm/v6/prisma-client/observability-and-logging/metrics.mdx index 9a78fc364d..a7145043b4 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/observability-and-logging/metrics.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/observability-and-logging/metrics.mdx @@ -11,7 +11,7 @@ Prisma Client metrics give you a detailed insight into how Prisma Client interac :::danger[`metrics` preview feature has been removed ] -The `metrics` preview feature has been **removed** as of [Prisma ORM v7.0.0](https://github.com/prisma/prisma/releases/tag/7.0.0). +The `metrics` preview feature has been **removed** as of [Prisma ORM v7.0.0](https://github.com/prisma/orm/releases/tag/7.0.0). If you need visibility into query or connection pool behavior, we recommend using the _native metrics provided by your database driver_ (for example, pool statistics) or setting up _OpenTelemetry_ for observability across your whole application. diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/aggregation-grouping-summarizing.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/aggregation-grouping-summarizing.mdx index e78d901f8d..288eaec73e 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/aggregation-grouping-summarizing.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/aggregation-grouping-summarizing.mdx @@ -49,7 +49,7 @@ console.log("Average age:" + aggregations._avg.age); ### Aggregate values are nullable -In [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0) and later, aggregations on **nullable fields** can return a `number` or `null`. This excludes `count`, which always returns 0 if no records are found. +In [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0) and later, aggregations on **nullable fields** can return a `number` or `null`. This excludes `count`, which always returns 0 if no records are found. Consider the following query, where `age` is nullable in the schema: @@ -84,7 +84,7 @@ This allows you to differentiate between the true aggregate value (which could b ## Group by -Prisma Client's [`groupBy()`](/orm/v6/reference/prisma-client-reference#groupby) allows you to **group records** by one or more field values - such as `country`, or `country` and `city` and **perform aggregations** on each group, such as finding the average age of people living in a particular city. `groupBy()` is a GA in [2.20.0](https://github.com/prisma/prisma/releases/2.20.0) and later. +Prisma Client's [`groupBy()`](/orm/v6/reference/prisma-client-reference#groupby) allows you to **group records** by one or more field values - such as `country`, or `country` and `city` and **perform aggregations** on each group, such as finding the average age of people living in a particular city. `groupBy()` is a GA in [2.20.0](https://github.com/prisma/orm/releases/2.20.0) and later. The following video uses `groupBy()` to summarize total COVID-19 cases by continent: @@ -236,7 +236,7 @@ The following constraints apply when you combine `groupBy()` and `orderBy`: #### Order by aggregate group -You can **order by aggregate group**. Prisma ORM added support for using `orderBy` with aggregated groups in relational databases in version [2.21.0](https://github.com/prisma/prisma/releases/2.21.0) and support for MongoDB in [3.4.0](https://github.com/prisma/prisma/releases/3.4.0). +You can **order by aggregate group**. Prisma ORM added support for using `orderBy` with aggregated groups in relational databases in version [2.21.0](https://github.com/prisma/orm/releases/2.21.0) and support for MongoDB in [3.4.0](https://github.com/prisma/orm/releases/3.4.0). The following example sorts each `city` group by the number of users in that group (largest group first): @@ -308,7 +308,7 @@ const userCount = await prisma.user.count(); :::info -This feature is generally available in version [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later. To use this feature in versions before 3.0.1 the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `selectRelationCount` will need to be enabled. +This feature is generally available in version [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later. To use this feature in versions before 3.0.1 the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `selectRelationCount` will need to be enabled. ::: @@ -413,7 +413,7 @@ const usersWithCount = await prisma.user.findMany({ :::info -This feature is generally available in version `4.16.0` and later. To use this feature in versions [`4.3.0`](https://github.com/prisma/prisma/releases/tag/4.3.0) to [`4.15.0`](https://github.com/prisma/prisma/releases/tag/4.15.0) the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `filteredRelationCount` will need to be enabled. +This feature is generally available in version `4.16.0` and later. To use this feature in versions [`4.3.0`](https://github.com/prisma/orm/releases/tag/4.3.0) to [`4.15.0`](https://github.com/prisma/orm/releases/tag/4.15.0) the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `filteredRelationCount` will need to be enabled. ::: @@ -454,7 +454,7 @@ await prisma.user.findMany({ ### Count non-`null` field values -In [2.15.0](https://github.com/prisma/prisma/releases/2.15.0) and later, you can count all records as well as all instances of non-`null` field values. The following query returns a count of: +In [2.15.0](https://github.com/prisma/orm/releases/2.15.0) and later, you can count all records as well as all instances of non-`null` field values. The following query returns a count of: - All `User` records (`_all`) - All non-`null` `name` values (not distinct values, just values that are not `null`) diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/crud.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/crud.mdx index ee81ba541c..bb8406df37 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/crud.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/crud.mdx @@ -207,7 +207,7 @@ For more information about working with generated types, see: [Generated types]( ### Create multiple records -Prisma Client supports bulk inserts as a GA feature in [2.20.0](https://github.com/prisma/prisma/releases/2.20.0) and later. +Prisma Client supports bulk inserts as a GA feature in [2.20.0](https://github.com/prisma/orm/releases/2.20.0) and later. The following [`createMany()`](/orm/v6/reference/prisma-client-reference#createmany) query creates multiple users and skips any duplicates (`email` must be unique): @@ -764,7 +764,7 @@ Be aware that this query will fail if the user has any related records (such as :::warning -In [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0) and later it is possible to do cascading deletes using the **preview feature** [referential actions](/orm/v6/prisma-schema/data-model/relations/referential-actions). +In [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0) and later it is possible to do cascading deletes using the **preview feature** [referential actions](/orm/v6/prisma-schema/data-model/relations/referential-actions). ::: diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/filtering-and-sorting.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/filtering-and-sorting.mdx index 83e495f2b5..5bd7795cda 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/filtering-and-sorting.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/filtering-and-sorting.mdx @@ -331,7 +331,7 @@ const posts = await prisma.post.findMany({ ### Sort by relation aggregate value -In [2.19.0](https://github.com/prisma/prisma/releases/2.19.0) and later, you can sort by the **count of related records**. +In [2.19.0](https://github.com/prisma/orm/releases/2.19.0) and later, you can sort by the **count of related records**. For example, the following query sorts users by the number of related posts: @@ -346,11 +346,11 @@ const getActiveUsers = await prisma.user.findMany({ }); ``` -> **Note**: It is not currently possible to [return the count of a relation](https://github.com/prisma/prisma/issues/5079). +> **Note**: It is not currently possible to [return the count of a relation](https://github.com/prisma/orm/issues/5079). ### Sort by relevance (PostgreSQL and MySQL) -In [3.5.0+](https://github.com/prisma/prisma/releases/3.5.0) for PostgreSQL and [3.8.0+](https://github.com/prisma/prisma/releases/3.8.0) for MySQL, you can sort records by relevance to the query using the `_relevance` keyword. This uses the relevance ranking functions from full text search features. +In [3.5.0+](https://github.com/prisma/orm/releases/3.5.0) for PostgreSQL and [3.8.0+](https://github.com/prisma/orm/releases/3.8.0) for MySQL, you can sort records by relevance to the query using the `_relevance` keyword. This uses the relevance ranking functions from full text search features. This feature is further explain in [the PostgreSQL documentation](https://www.postgresql.org/docs/12/textsearch-controls.html) and [the MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/fulltext-search.html). @@ -395,7 +395,7 @@ Prior to Prisma ORM 5.16.0, enabling the `fullTextSearch` preview feature would Notes: -- This feature is generally available in version `4.16.0` and later. To use this feature in versions [`4.1.0`](https://github.com/prisma/prisma/releases/tag/4.1.0) to [`4.15.0`](https://github.com/prisma/prisma/releases/tag/4.15.0) the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `orderByNulls` will need to be enabled. +- This feature is generally available in version `4.16.0` and later. To use this feature in versions [`4.1.0`](https://github.com/prisma/orm/releases/tag/4.1.0) to [`4.15.0`](https://github.com/prisma/orm/releases/tag/4.15.0) the [Preview feature](/orm/v6/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature) `orderByNulls` will need to be enabled. - This feature is not available for MongoDB. - You can only sort by nulls on optional [scalar](/orm/v6/prisma-schema/data-model/models#scalar-fields) fields. If you try to sort by nulls on a required or [relation](/orm/v6/prisma-schema/data-model/models#relation-fields) field, Prisma Client throws a [P2009 error](/orm/v6/reference/error-reference#p2009). diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/full-text-search.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/full-text-search.mdx index f88d153e13..d080a6a6a7 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/full-text-search.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/full-text-search.mdx @@ -48,7 +48,7 @@ const result = await prisma.posts.findMany({ }); ``` -> **Note**: There currently is a [known issue](https://github.com/prisma/prisma/issues/23627) in the full-text search feature for PostgreSQL. If you observe slow search queries, you can [optimize your query with raw SQL](#full-text-search-with-raw-sql). +> **Note**: There currently is a [known issue](https://github.com/prisma/orm/issues/23627) in the full-text search feature for PostgreSQL. If you observe slow search queries, you can [optimize your query with raw SQL](#full-text-search-with-raw-sql). ## Querying the database @@ -191,7 +191,7 @@ const posts = await prisma.post.findMany({ ### PostgreSQL -Prisma Client does not currently support using indexes to speed up full text search. There is an existing [GitHub Issue](https://github.com/prisma/prisma/issues/8950) for this. +Prisma Client does not currently support using indexes to speed up full text search. There is an existing [GitHub Issue](https://github.com/prisma/orm/issues/8950) for this. ### MySQL @@ -246,7 +246,7 @@ However, if you try to search on `title` alone, the search will fail with the er ## Full-text search with raw SQL -Full-text search is currently in Preview, and due to a [known issue](https://github.com/prisma/prisma/issues/23627), you might experience slow search queries. If so, you can optimize your query using [TypedSQL](/orm/v6/prisma-client/using-raw-sql). +Full-text search is currently in Preview, and due to a [known issue](https://github.com/prisma/orm/issues/23627), you might experience slow search queries. If so, you can optimize your query using [TypedSQL](/orm/v6/prisma-client/using-raw-sql). ### PostgreSQL diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/query-optimization-performance.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/query-optimization-performance.mdx index 3128f97bf1..c8a4f1f03d 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/query-optimization-performance.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/query-optimization-performance.mdx @@ -236,7 +236,7 @@ Use `findUnique()` in combination with [the fluent API](/orm/v6/prisma-client/qu It may seem counterintuitive to use a `prisma.user.findUnique(...).posts()` query to return posts instead of `prisma.posts.findMany()` - particularly as the former results in two queries rather than one. -The **only** reason you need to use the fluent API (`user.findUnique(...).posts()`) to return posts is that the dataloader in Prisma Client batches `findUnique()` queries and does not currently [batch `findMany()` queries](https://github.com/prisma/prisma/issues/1477). +The **only** reason you need to use the fluent API (`user.findUnique(...).posts()`) to return posts is that the dataloader in Prisma Client batches `findUnique()` queries and does not currently [batch `findMany()` queries](https://github.com/prisma/orm/issues/1477). When the dataloader batches `findMany()` queries or your query has the `relationStrategy` set to `join`, you no longer need to use `findUnique()` with the fluent API in this way. diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/relation-queries.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/relation-queries.mdx index f454b0903e..9262e7a006 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/relation-queries.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/relation-queries.mdx @@ -23,9 +23,9 @@ Nested reads allow you to read related data from multiple tables in your databas ### Relation load strategies (Preview) -Since version [5.8.0](https://github.com/prisma/prisma/releases/tag/5.8.0), you can decide on a per-query-level _how_ you want Prisma Client to execute a relation query (i.e. what _load strategy_ should be applied) via the `relationLoadStrategy` option for PostgreSQL databases. +Since version [5.8.0](https://github.com/prisma/orm/releases/tag/5.8.0), you can decide on a per-query-level _how_ you want Prisma Client to execute a relation query (i.e. what _load strategy_ should be applied) via the `relationLoadStrategy` option for PostgreSQL databases. -Since version [5.10.0](https://github.com/prisma/prisma/releases/tag/5.10.0), this feature is also available for MySQL. +Since version [5.10.0](https://github.com/prisma/orm/releases/tag/5.10.0), this feature is also available for MySQL. Because the `relationLoadStrategy` option is currently in Preview, you need to enable it via the `relationJoins` preview feature flag in your Prisma schema file: @@ -326,7 +326,7 @@ const user = await prisma.user.findFirst({ ## Relation count -In [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later, you can [`include` or `select` a count of relations](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields - for example, a user's post count. +In [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later, you can [`include` or `select` a count of relations](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields - for example, a user's post count. ```ts const relationCount = await prisma.user.findMany({ diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/select-fields.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/select-fields.mdx index fbd71e6d98..0ba423656a 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/select-fields.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/select-fields.mdx @@ -63,7 +63,7 @@ In all cases, the query result will be statically typed, ensuring that you don't Selecting only the fields and relations that you require rather than relying on the default selection set can reduce the size of the response and improve query speed. -Since version [5.9.0](https://github.com/prisma/prisma/releases/tag/5.9.0), when doing a relation query with `include` or by using `select` on a relation field, you can also specify the `relationLoadStrategy` to decide whether you want to use a database-level join or perform multiple queries and merge the data on the application level. This feature is currently in [Preview](/orm/v6/more/releases#preview), you can learn more about it [here](/orm/v6/prisma-client/queries/relation-queries#relation-load-strategies-preview). +Since version [5.9.0](https://github.com/prisma/orm/releases/tag/5.9.0), when doing a relation query with `include` or by using `select` on a relation field, you can also specify the `relationLoadStrategy` to decide whether you want to use a database-level join or perform multiple queries and merge the data on the application level. This feature is currently in [Preview](/orm/v6/more/releases#preview), you can learn more about it [here](/orm/v6/prisma-client/queries/relation-queries#relation-load-strategies-preview). ## Example schema @@ -270,4 +270,4 @@ Notice how the returned object does _not_ contain the `password` field. ## Relation count -In [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later, you can `include` or `select` a [count of relations](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields. For example, a user's post count. +In [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later, you can `include` or `select` a [count of relations](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields. For example, a user's post count. diff --git a/apps/docs/content/docs/orm/v6/prisma-client/setup-and-configuration/read-replicas.mdx b/apps/docs/content/docs/orm/v6/prisma-client/setup-and-configuration/read-replicas.mdx index 327a0ea847..3d78fc99bf 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/setup-and-configuration/read-replicas.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/setup-and-configuration/read-replicas.mdx @@ -8,7 +8,7 @@ metaDescription: Learn how to set up and use read replicas with Prisma Client Read replicas enable you to distribute workloads across database replicas for high-traffic workloads. The [read replicas extension](https://github.com/prisma/extension-read-replicas), `@prisma/extension-read-replicas`, adds support for read-only database replicas to Prisma Client. -The read replicas extension supports Prisma ORM versions [5.2.0](https://github.com/prisma/prisma/releases/tag/5.2.0) and higher. For Prisma 7.0+, the extension requires passing full PrismaClient instances instead of connection URLs. If you run into a bug or have feedback, create a GitHub issue [here](https://github.com/prisma/extension-read-replicas/issues/new). +The read replicas extension supports Prisma ORM versions [5.2.0](https://github.com/prisma/orm/releases/tag/5.2.0) and higher. For Prisma 7.0+, the extension requires passing full PrismaClient instances instead of connection URLs. If you run into a bug or have feedback, create a GitHub issue [here](https://github.com/prisma/extension-read-replicas/issues/new). ## Setup the read replicas extension diff --git a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/index.mdx b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/index.mdx index 32e30af58c..7348d88f65 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/index.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/index.mdx @@ -40,7 +40,7 @@ const newTypes = await prisma.sample.create({ :::warning -The use of the `Decimal` field [is not currently supported in MongoDB](https://github.com/prisma/prisma/issues/12637). +The use of the `Decimal` field [is not currently supported in MongoDB](https://github.com/prisma/orm/issues/12637). ::: @@ -109,7 +109,7 @@ Learn more in the [upgrade guide to v6](/orm/v6/more/upgrades/to-v7). :::note -There currently is a [bug](https://github.com/prisma/prisma/issues/9516) that doesn't allow you to pass in `DateTime` values as strings and produces a runtime error when you do. `DateTime` values need to be passed as [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) objects (i.e. `new Date('2024-12-04')` instead of `'2024-12-04'`). +There currently is a [bug](https://github.com/prisma/orm/issues/9516) that doesn't allow you to pass in `DateTime` values as strings and produces a runtime error when you do. `DateTime` values need to be passed as [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) objects (i.e. `new Date('2024-12-04')` instead of `'2024-12-04'`). ::: diff --git a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields.mdx b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields.mdx index 386078ae7f..24ef5986cd 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields.mdx @@ -928,7 +928,7 @@ For a complete guide on configuration, monorepo setup, and other advanced featur ### Can you select a subset of JSON key/values to return? -No - it is not yet possible to [select which JSON elements to return](https://github.com/prisma/prisma/issues/2431). Prisma Client returns the entire JSON object. +No - it is not yet possible to [select which JSON elements to return](https://github.com/prisma/orm/issues/2431). Prisma Client returns the entire JSON object. ### Can you filter on the presence of a specific key? @@ -940,7 +940,7 @@ Yes - case-insensitive filtering for `Json` fields is supported since version 6. ### Can you sort an object property within a JSON value? -No, [sorting object properties within a JSON value](https://github.com/prisma/prisma/issues/10346) (order-by-prop) is not currently supported. +No, [sorting object properties within a JSON value](https://github.com/prisma/orm/issues/10346) (order-by-prop) is not currently supported. ### How to set a default value for JSON fields? diff --git a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-scalar-lists-arrays.mdx b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-scalar-lists-arrays.mdx index c678d6ffe4..208ea169fa 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-scalar-lists-arrays.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/special-fields-and-types/working-with-scalar-lists-arrays.mdx @@ -48,7 +48,7 @@ const createdUser = await prisma.user.create({ :::warning This method is available on MongoDB only in versions -[3.11.1](https://github.com/prisma/prisma/releases/tag/3.11.1) and later. +[3.11.1](https://github.com/prisma/orm/releases/tag/3.11.1) and later. ::: @@ -73,9 +73,9 @@ Unlike `set: null`, `unset` removes the list entirely. Available for: -- PostgreSQL in versions [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) and later -- CockroachDB in versions [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) and later -- MongoDB in versions [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) and later +- PostgreSQL in versions [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) and later +- CockroachDB in versions [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) and later +- MongoDB in versions [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) and later ::: @@ -127,9 +127,9 @@ if (user) { Available for: -- PostgreSQL in versions [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) and later -- CockroachDB in versions [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) and later -- MongoDB in versions [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) and later +- PostgreSQL in versions [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) and later +- CockroachDB in versions [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) and later +- MongoDB in versions [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) and later ::: @@ -151,8 +151,8 @@ const posts = await prisma.post.findMany({ This section applies to: -- PostgreSQL in versions [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) and later -- CockroachDB in versions [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) and later +- PostgreSQL in versions [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) and later +- CockroachDB in versions [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) and later ::: diff --git a/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/legacy-migrate.mdx b/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/legacy-migrate.mdx index 04c8c8c558..30f7bdba3f 100644 --- a/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/legacy-migrate.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/legacy-migrate.mdx @@ -7,7 +7,7 @@ metaTitle: Legacy Prisma Migrate metaDescription: Legacy Prisma Migrate is a declarative data modeling and schema migration tool that is available via the Prisma CLI. --- -> **Important!** This page documents legacy Prisma Migrate (Experimental) available in version 2.12.0 and earlier. [Prisma Migrate](/orm/v6/prisma-migrate/getting-started) is available in version [2.13.0](https://github.com/prisma/prisma/releases/tag/2.13.0) and Generally Available in [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0). +> **Important!** This page documents legacy Prisma Migrate (Experimental) available in version 2.12.0 and earlier. [Prisma Migrate](/orm/v6/prisma-migrate/getting-started) is available in version [2.13.0](https://github.com/prisma/orm/releases/tag/2.13.0) and Generally Available in [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0). Legacy Prisma Migrate is a tool that lets you _change your database schema_, e.g. by creating new tables or adding columns to existing tables. These changes are called _schema migrations_. legacy Prisma Migrate is available as part of the [Prisma CLI](/orm/v6/tools/prisma-cli#installation) via the `legacy Prisma Migrate` command. diff --git a/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx b/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx index 6bf8dba2f3..bc39fb2578 100644 --- a/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx @@ -16,7 +16,7 @@ Prisma Migrate does not currently support the MongoDB connector. Prisma Migrate generates SQL files that are specific to your provider. This means that you cannot use the same migration files for PostgreSQL in production and SQLite in development, because the syntax in the migrations will be incompatible. -In [2.15.0](https://github.com/prisma/prisma/releases/2.15.0) and later, Prisma Migrate detects when the migrations do not match the configured provider and prints an error message. For example, if your migrations are for a PostgreSQL database but your `provider` is set to `mysql`: +In [2.15.0](https://github.com/prisma/orm/releases/2.15.0) and later, Prisma Migrate detects when the migrations do not match the configured provider and prints an error message. For example, if your migrations are for a PostgreSQL database but your `provider` is set to `mysql`: ``` Error: P3014 diff --git a/apps/docs/content/docs/orm/v6/prisma-migrate/workflows/patching-and-hotfixing.mdx b/apps/docs/content/docs/orm/v6/prisma-migrate/workflows/patching-and-hotfixing.mdx index e74ca4170d..e2443a6322 100644 --- a/apps/docs/content/docs/orm/v6/prisma-migrate/workflows/patching-and-hotfixing.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-migrate/workflows/patching-and-hotfixing.mdx @@ -260,7 +260,7 @@ Your local migration history now yields the same result as the state your produc :::info -This does not apply from version [3.12.0](https://github.com/prisma/prisma/releases/tag/3.12.0) upwards. +This does not apply from version [3.12.0](https://github.com/prisma/orm/releases/tag/3.12.0) upwards. ::: @@ -275,4 +275,4 @@ Error: undefined: Database error Error querying the database: db error: ERROR: prepared statement "s0" already exists ``` -See [Prisma Migrate and PgBouncer workaround](/orm/v6/prisma-client/setup-and-configuration/databases-connections/pgbouncer) for further information and a workaround. Follow [GitHub issue #6485](https://github.com/prisma/prisma/issues/6485) for updates. +See [Prisma Migrate and PgBouncer workaround](/orm/v6/prisma-client/setup-and-configuration/databases-connections/pgbouncer) for further information and a workaround. Follow [GitHub issue #6485](https://github.com/prisma/orm/issues/6485) for updates. diff --git a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/database-mapping.mdx b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/database-mapping.mdx index c2d1b65cda..9d506484b4 100644 --- a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/database-mapping.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/database-mapping.mdx @@ -105,7 +105,7 @@ There is currently a known bug in Prisma ORM v7 where using mapped enum values w ## Constraint and index names -You can optionally use the `map` argument to explicitly define the **underlying constraint and index names** in the Prisma schema for the attributes [`@id`](/orm/v6/reference/prisma-schema-reference#id), [`@@id`](/orm/v6/reference/prisma-schema-reference#id-1), [`@unique`](/orm/v6/reference/prisma-schema-reference#unique), [`@@unique`](/orm/v6/reference/prisma-schema-reference#unique-1), [`@@index`](/orm/v6/reference/prisma-schema-reference#index) and [`@relation`](/orm/v6/reference/prisma-schema-reference#relation). (This is available in Prisma ORM version [2.29.0](https://github.com/prisma/prisma/releases/tag/2.29.0) and later.) +You can optionally use the `map` argument to explicitly define the **underlying constraint and index names** in the Prisma schema for the attributes [`@id`](/orm/v6/reference/prisma-schema-reference#id), [`@@id`](/orm/v6/reference/prisma-schema-reference#id-1), [`@unique`](/orm/v6/reference/prisma-schema-reference#unique), [`@@unique`](/orm/v6/reference/prisma-schema-reference#unique-1), [`@@index`](/orm/v6/reference/prisma-schema-reference#index) and [`@relation`](/orm/v6/reference/prisma-schema-reference#relation). (This is available in Prisma ORM version [2.29.0](https://github.com/prisma/orm/releases/tag/2.29.0) and later.) When introspecting a database, the `map` argument will _only_ be rendered in the schema if the name _differs_ from Prisma ORM's [default constraint naming convention for indexes and constraints](#prisma-orms-default-naming-conventions-for-indexes-and-constraints). diff --git a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/models.mdx b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/models.mdx index dd2f4bea53..c04fa7443a 100644 --- a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/models.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/models.mdx @@ -377,7 +377,7 @@ Refer to the [relations documentation](/orm/v6/prisma-schema/data-model/relation ### Native types mapping -Version [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later support **native database type attributes** (type attributes) that describe the underlying database type: +Version [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later support **native database type attributes** (type attributes) that describe the underlying database type: ```prisma highlight=3;normal model Post { diff --git a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/views.mdx b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/views.mdx index aa3cf1f260..5172bb926a 100644 --- a/apps/docs/content/docs/orm/v6/prisma-schema/data-model/views.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-schema/data-model/views.mdx @@ -18,7 +18,7 @@ The `views` preview feature allows you to represent views in your Prisma schema :::warning -Support for views is currently a [Preview](/orm/v6/more/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag.

For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/prisma/issues/17335). +Support for views is currently a [Preview](/orm/v6/more/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag.

For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/orm/issues/17335). ::: @@ -34,7 +34,7 @@ generator client { } ``` -Please leave feedback about this preview feature in our dedicated preview feature [feedback issue](https://github.com/prisma/prisma/issues/17335) for `views`. +Please leave feedback about this preview feature in our dedicated preview feature [feedback issue](https://github.com/prisma/orm/issues/17335) for `views`. ## Create a view in the underlying database @@ -279,7 +279,7 @@ Materialized views persist the result of the view query for faster access and on Currently, Prisma ORM does not support materialized views. However, when you [manually create a view](#create-a-view-in-the-underlying-database), you can also create a materialized view with the corresponding command in the underlying database. You can then use Prisma Client's [TypedSQL functionality](/orm/v6/prisma-client/using-raw-sql) to execute the command and refresh the view manually. -In the future Prisma Client might support marking individual views as materialized and add a Prisma Client method to refresh the materialized view. Please comment on our [`views` feedback issue](https://github.com/prisma/prisma/issues/17335) with your use case. +In the future Prisma Client might support marking individual views as materialized and add a Prisma Client method to refresh the materialized view. Please comment on our [`views` feedback issue](https://github.com/prisma/orm/issues/17335) with your use case. ## Limitations diff --git a/apps/docs/content/docs/orm/v6/prisma-schema/introspection.mdx b/apps/docs/content/docs/orm/v6/prisma-schema/introspection.mdx index fae09de20a..57cc38442a 100644 --- a/apps/docs/content/docs/orm/v6/prisma-schema/introspection.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-schema/introspection.mdx @@ -338,7 +338,7 @@ Use cases include: ## Introspecting only a subset of your database schema -Introspecting only a subset of your database schema is [not yet officially supported](https://github.com/prisma/prisma/issues/807) by Prisma ORM. +Introspecting only a subset of your database schema is [not yet officially supported](https://github.com/prisma/orm/issues/807) by Prisma ORM. However, you can achieve this by creating a new database user that only has access to the tables which you'd like to see represented in your Prisma schema, and then perform the introspection using that user. The introspection will then only include the tables the new user has access to. @@ -352,21 +352,21 @@ For these features, the Prisma CLI will surface detect usage of the feature in y The `prisma db pull` command will surface the following unsupported features: -- From version [4.13.0](https://github.com/prisma/prisma/releases/tag/4.13.0): - - [Partitioned tables](https://github.com/prisma/prisma/issues/1708) - - [PostgreSQL Row Level Security](https://github.com/prisma/prisma/issues/12735) - - [Index sort order, `NULLS FIRST` / `NULLS LAST`](https://github.com/prisma/prisma/issues/15466) - - [CockroachDB row-level TTL](https://github.com/prisma/prisma/issues/13982) - - [Comments](https://github.com/prisma/prisma/issues/8703) - - [PostgreSQL deferred constraints](https://github.com/prisma/prisma/issues/8807) -- From version [4.14.0](https://github.com/prisma/prisma/releases/tag/4.14.0): - - [Check Constraints](https://github.com/prisma/prisma/issues/3388) (MySQL + PostgreSQL) - - [Exclusion Constraints](https://github.com/prisma/prisma/issues/17514) - - [MongoDB $jsonSchema](https://github.com/prisma/prisma/issues/8135) -- From version [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0): - - [Expression indexes](https://github.com/prisma/prisma/issues/2504) - -You can find the list of features we intend to support on [GitHub (labeled with `topic:database-functionality`)](https://github.com/prisma/prisma/issues?q=is%3Aopen+label%3A%22topic%3A+database-functionality%22+label%3Ateam%2Fschema+sort%3Aupdated-desc+). +- From version [4.13.0](https://github.com/prisma/orm/releases/tag/4.13.0): + - [Partitioned tables](https://github.com/prisma/orm/issues/1708) + - [PostgreSQL Row Level Security](https://github.com/prisma/orm/issues/12735) + - [Index sort order, `NULLS FIRST` / `NULLS LAST`](https://github.com/prisma/orm/issues/15466) + - [CockroachDB row-level TTL](https://github.com/prisma/orm/issues/13982) + - [Comments](https://github.com/prisma/orm/issues/8703) + - [PostgreSQL deferred constraints](https://github.com/prisma/orm/issues/8807) +- From version [4.14.0](https://github.com/prisma/orm/releases/tag/4.14.0): + - [Check Constraints](https://github.com/prisma/orm/issues/3388) (MySQL + PostgreSQL) + - [Exclusion Constraints](https://github.com/prisma/orm/issues/17514) + - [MongoDB $jsonSchema](https://github.com/prisma/orm/issues/8135) +- From version [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0): + - [Expression indexes](https://github.com/prisma/orm/issues/2504) + +You can find the list of features we intend to support on [GitHub (labeled with `topic:database-functionality`)](https://github.com/prisma/orm/issues?q=is%3Aopen+label%3A%22topic%3A+database-functionality%22+label%3Ateam%2Fschema+sort%3Aupdated-desc+). ### Workaround for introspection warnings for unsupported features diff --git a/apps/docs/content/docs/orm/v6/prisma-schema/overview/data-sources.mdx b/apps/docs/content/docs/orm/v6/prisma-schema/overview/data-sources.mdx index a323d87e75..ee9850cc23 100644 --- a/apps/docs/content/docs/orm/v6/prisma-schema/overview/data-sources.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-schema/overview/data-sources.mdx @@ -24,7 +24,7 @@ A Prisma schema can only have _one_ data source. However, you can: - [Programmatically override a data source `url` when creating your `PrismaClient`](/orm/v6/reference/prisma-client-reference#programmatically-override-a-datasource-url) - [Specify a different URL for Prisma Migrate's shadow database if you are working with cloud-hosted development databases](/orm/v6/prisma-migrate/understanding-prisma-migrate/shadow-database#cloud-hosted-shadow-databases-must-be-created-manually) -> **Note**: Multiple provider support was removed in 2.22.0. Please see [Deprecation of provider array notation](https://github.com/prisma/prisma/issues/3834) for more information. +> **Note**: Multiple provider support was removed in 2.22.0. Please see [Deprecation of provider array notation](https://github.com/prisma/orm/issues/3834) for more information. ## Securing database connections diff --git a/apps/docs/content/docs/orm/v6/reference/environment-variables-reference.mdx b/apps/docs/content/docs/orm/v6/reference/environment-variables-reference.mdx index 5fa0552c16..ca58ac869a 100644 --- a/apps/docs/content/docs/orm/v6/reference/environment-variables-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/environment-variables-reference.mdx @@ -258,7 +258,7 @@ PRISMA_SCHEMA_ENGINE_BINARY=custom/my-schema-engine-unix :::warning -**Deprecated**: `PRISMA_MIGRATION_ENGINE_BINARY` variable is deprecated in [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) because Migration engine was renamed to Schema Engine. +**Deprecated**: `PRISMA_MIGRATION_ENGINE_BINARY` variable is deprecated in [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) because Migration engine was renamed to Schema Engine. ::: @@ -284,7 +284,7 @@ PRISMA_INTROSPECTION_ENGINE_BINARY=custom/my-introspection-engine-unix :::warning -The Introspection Engine is served by the Migration Engine from [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used. +The Introspection Engine is served by the Migration Engine from [4.9.0](https://github.com/prisma/orm/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used. ::: @@ -304,7 +304,7 @@ PRISMA_FMT_BINARY=custom/my-custom-format-engine-unix :::warning -The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/prisma/prisma/releases/tag/4.2.0) or lower. +The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/prisma/orm/releases/tag/4.2.0) or lower. ::: diff --git a/apps/docs/content/docs/orm/v6/reference/error-reference.mdx b/apps/docs/content/docs/orm/v6/reference/error-reference.mdx index 3f94405cb8..8754d43f2a 100644 --- a/apps/docs/content/docs/orm/v6/reference/error-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/error-reference.mdx @@ -332,7 +332,7 @@ Possible P1012 error messages: :::warning -The Schema Engine was previously called Migration Engine. This change was introduced in version [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0). +The Schema Engine was previously called Migration Engine. This change was introduced in version [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0). ::: @@ -390,7 +390,7 @@ The Schema Engine was previously called Migration Engine. This change was introd #### `P3013` -"Datasource provider arrays are no longer supported in migrate. Please change your datasource to use a single provider. Read more at [https://pris.ly/multi-provider-deprecation](https://pris.ly/multi-provider-deprecation)" +"Datasource provider arrays are no longer supported in migrate. Please change your datasource to use a single provider. Read more at [https://pris.ly/multi-provider-deprecation](https://github.com/prisma/orm/issues/3834)" #### `P3014` diff --git a/apps/docs/content/docs/orm/v6/reference/preview-features/cli-preview-features.mdx b/apps/docs/content/docs/orm/v6/reference/preview-features/cli-preview-features.mdx index 22bf11933f..65cf996468 100644 --- a/apps/docs/content/docs/orm/v6/reference/preview-features/cli-preview-features.mdx +++ b/apps/docs/content/docs/orm/v6/reference/preview-features/cli-preview-features.mdx @@ -20,7 +20,7 @@ In the list below, you can find a history of Prisma CLI features that were in Pr | Features | Released in Preview | Released in general availability | | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------- | -| [`prisma migrate diff`](/orm/v6/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/prisma/releases/tag/3.13.0) | -| [`prisma db execute`](/orm/v6/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/prisma/releases/tag/3.13.0) | -| [`prisma db push`](/orm/v6/prisma-migrate/workflows/prototyping-your-schema) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | [2.22.0](https://github.com/prisma/prisma/releases/tag/2.22.0) | -| [`prisma migrate`](/orm/v6/prisma-migrate/getting-started) | [2.13.0](https://github.com/prisma/prisma/releases/tag/2.13.0) | [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0) | +| [`prisma migrate diff`](/orm/v6/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/orm/releases/tag/3.13.0) | +| [`prisma db execute`](/orm/v6/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/orm/releases/tag/3.13.0) | +| [`prisma db push`](/orm/v6/prisma-migrate/workflows/prototyping-your-schema) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | [2.22.0](https://github.com/prisma/orm/releases/tag/2.22.0) | +| [`prisma migrate`](/orm/v6/prisma-migrate/getting-started) | [2.13.0](https://github.com/prisma/orm/releases/tag/2.13.0) | [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0) | diff --git a/apps/docs/content/docs/orm/v6/reference/preview-features/client-preview-features.mdx b/apps/docs/content/docs/orm/v6/reference/preview-features/client-preview-features.mdx index a22ab7e43a..b8d29aad36 100644 --- a/apps/docs/content/docs/orm/v6/reference/preview-features/client-preview-features.mdx +++ b/apps/docs/content/docs/orm/v6/reference/preview-features/client-preview-features.mdx @@ -16,16 +16,16 @@ The following [Preview](/orm/v6/more/releases#preview) feature flags are availab | Feature | Released into Preview | Feedback issue | | ------------------------------------------------------------------------------- | :------------------------------------------------------------- | :-------------------------------------------------------------------: | -| [`metrics`](/orm/v6/prisma-client/observability-and-logging/metrics) | [3.15.0](https://github.com/prisma/prisma/releases/tag/3.15.0) | [Submit feedback](https://github.com/prisma/prisma/issues/13579) | -| [`views`](/orm/v6/prisma-schema/data-model/views) | [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0) | [Submit feedback](https://github.com/prisma/prisma/issues/17335) | -| `relationJoins` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22288) | -| `nativeDistinct` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22287) | -| `typedSql` | [5.19.0](https://github.com/prisma/prisma/releases/tag/5.19.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/25106) | -| `strictUndefinedChecks` | [5.20.0](https://github.com/prisma/prisma/releases/tag/5.20.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/25271) | -| [`fullTextSearchPostgres`](/orm/v6/prisma-client/queries/full-text-search) | [6.0.0](https://github.com/prisma/prisma/releases/tag/6.0.0) | [Submit feedback](https://github.com/prisma/prisma/issues/25773) | -| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/prisma/issues/) | +| [`metrics`](/orm/v6/prisma-client/observability-and-logging/metrics) | [3.15.0](https://github.com/prisma/orm/releases/tag/3.15.0) | [Submit feedback](https://github.com/prisma/orm/issues/13579) | +| [`views`](/orm/v6/prisma-schema/data-model/views) | [4.9.0](https://github.com/prisma/orm/releases/tag/4.9.0) | [Submit feedback](https://github.com/prisma/orm/issues/17335) | +| `relationJoins` | [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/orm/discussions/22288) | +| `nativeDistinct` | [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/orm/discussions/22287) | +| `typedSql` | [5.19.0](https://github.com/prisma/orm/releases/tag/5.19.0) | [Submit feedback](https://github.com/prisma/orm/discussions/25106) | +| `strictUndefinedChecks` | [5.20.0](https://github.com/prisma/orm/releases/tag/5.20.0) | [Submit feedback](https://github.com/prisma/orm/discussions/25271) | +| [`fullTextSearchPostgres`](/orm/v6/prisma-client/queries/full-text-search) | [6.0.0](https://github.com/prisma/orm/releases/tag/6.0.0) | [Submit feedback](https://github.com/prisma/orm/issues/25773) | +| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/orm/issues/) | -To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). +To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/orm/issues/3108). ## Enabling a Prisma Client Preview feature @@ -55,39 +55,39 @@ In the list below, you can find a history of Prisma Client and Prisma schema fea | Feature | Released into Preview | Released into General Availability | | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`driverAdapters`](/orm/v6/overview/databases/database-drivers#driver-adapters) | [5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0) | [6.16.0](https://github.com/prisma/prisma/releases/tag/6.16.0) | -| [`queryCompiler`](/orm/v6/prisma-client/setup-and-configuration/no-rust-engine) | [6.7.0](https://github.com/prisma/prisma/releases/tag/6.15.0) | [6.16.0](https://github.com/prisma/prisma/releases/tag/6.16.0) | -| [`multiSchema`](/orm/v6/prisma-schema/data-model/multi-schema) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [6.13.0](https://github.com/prisma/prisma/releases/tag/6.13.0) | -| [`prismaSchemaFolder`](/orm/v6/prisma-schema/overview/location#multi-file-prisma-schema) | [5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0) | [6.7.0](https://pris.ly/release/6.7.0) | -| `omitApi` | [5.13.0](https://github.com/prisma/prisma/releases/tag/5.13.0) | [6.2.0](https://github.com/prisma/prisma/releases/tag/6.2.0) | -| `jsonProtocol` | [4.11.0](https://github.com/prisma/prisma/releases/tag/4.11.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`extendedWhereUnique`](/orm/v6/reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) | [4.5.0](https://github.com/prisma/prisma/releases/tag/4.5.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`fieldReference`](/orm/v6/reference/prisma-client-reference#compare-columns-in-the-same-table) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`clientExtensions`](/orm/v6/prisma-client/client-extensions) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`filteredRelationCount`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#filter-the-relation-count) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`tracing`](/orm/v6/prisma-client/observability-and-logging/opentelemetry-tracing) | [4.2.0](https://github.com/prisma/prisma/releases/tag/4.2.0) | [6.1.0](https://github.com/prisma/prisma/releases/tag/6.1.0) | -| [`orderByNulls`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last) | [4.1.0](https://github.com/prisma/prisma/releases/tag/4.1.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`referentialIntegrity`](/orm/v6/prisma-schema/data-model/relations/relation-mode) | [3.1.1](https://github.com/prisma/prisma/releases/tag/3.1.1) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0) | -| [`interactiveTransactions`](/orm/v6/prisma-client/queries/transactions#interactive-transactions) | [2.29.0](https://github.com/prisma/prisma/releases/tag/2.29.0) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0)
with Prisma Accelerate [5.1.1](https://github.com/prisma/prisma/releases/tag/5.1.1) | -| [`extendedIndexes`](/orm/v6/prisma-schema/data-model/indexes) | [3.5.0](https://github.com/prisma/prisma/releases/tag/3.5.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`filterJson`](/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields#filter-on-a-json-field-simple) | [2.23.0](https://github.com/prisma/prisma/releases/tag/2.23.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`improvedQueryRaw`](/orm/v6/prisma-client/using-raw-sql/raw-queries#raw-query-type-mapping) | [3.14.0](https://github.com/prisma/prisma/releases/tag/3.14.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`cockroachdb`](/orm/v6/overview/databases/cockroachdb) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0)
migrations in [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) | [3.14.0](https://github.com/prisma/prisma/releases/tag/3.14.0) | -| [`mongodb`](/orm/v6/overview/databases/mongodb) | [2.27.0](https://github.com/prisma/prisma/releases/tag/2.27.0)
introspection in [3.2.0](https://github.com/prisma/prisma/releases/tag/3.2.0)
embedded docs in [3.4.0](https://github.com/prisma/prisma/releases/tag/3.4.0)
raw queries in [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0)
filters/ordering in embedded docs in [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) | [3.12.0](https://github.com/prisma/prisma/releases/tag/3.12.0) | -| [`microsoftSqlServer`](/orm/v6/overview/databases/sql-server) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`namedConstraints`](/orm/v6/prisma-schema/data-model/database-mapping#constraint-and-index-names) | [2.29.0](https://github.com/prisma/prisma/releases/tag/2.29.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`referentialActions`](/orm/v6/prisma-schema/data-model/relations/referential-actions) | [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`orderByAggregateGroup`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#order-by-aggregate-group) | [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`orderByRelation`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relation) | [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0)
aggregates in [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`selectRelationCount`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| `napi` | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`groupBy`](/orm/v6/reference/prisma-client-reference#groupby) | [2.14.0](https://github.com/prisma/prisma/releases/tag/2.14.0) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | -| [`createMany`](/orm/v6/reference/prisma-client-reference#createmany) | [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | -| [`nativeTypes`](/orm/v6/prisma-schema/data-model/models#native-types-mapping) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) | -| [`uncheckedScalarInputs`](/orm/v6/prisma-client/queries/relation-queries#create-a-single-record-and-multiple-related-records) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) | -| [`transactionApi`](/orm/v6/prisma-client/queries/transactions#the-transaction-api) | [2.1.0](https://github.com/prisma/prisma/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | -| [`connectOrCreate`](/orm/v6/reference/prisma-client-reference#connectorcreate) | [2.1.0](https://github.com/prisma/prisma/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | -| [`atomicNumberOperations`](/orm/v6/reference/prisma-client-reference#atomic-number-operations) | [2.6.0](https://github.com/prisma/prisma/releases/tag/2.6.0) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | -| [`insensitiveFilters` (PostgreSQL)](/orm/v6/prisma-client/queries/filtering-and-sorting#case-insensitive-filtering) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | [2.8.0](https://github.com/prisma/prisma/releases/tag/2.8.0) | -| [`aggregateApi`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#aggregate) | [2.2.0](https://github.com/prisma/prisma/releases/tag/2.2.0) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | -| [`distinct`](/orm/v6/reference/prisma-client-reference#distinct) | [2.3.0](https://github.com/prisma/prisma/releases/tag/2.3.0) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | +| [`driverAdapters`](/orm/v6/overview/databases/database-drivers#driver-adapters) | [5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0) | [6.16.0](https://github.com/prisma/orm/releases/tag/6.16.0) | +| [`queryCompiler`](/orm/v6/prisma-client/setup-and-configuration/no-rust-engine) | [6.7.0](https://github.com/prisma/orm/releases/tag/6.15.0) | [6.16.0](https://github.com/prisma/orm/releases/tag/6.16.0) | +| [`multiSchema`](/orm/v6/prisma-schema/data-model/multi-schema) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [6.13.0](https://github.com/prisma/orm/releases/tag/6.13.0) | +| [`prismaSchemaFolder`](/orm/v6/prisma-schema/overview/location#multi-file-prisma-schema) | [5.15.0](https://github.com/prisma/orm/releases/tag/5.15.0) | [6.7.0](https://pris.ly/release/6.7.0) | +| `omitApi` | [5.13.0](https://github.com/prisma/orm/releases/tag/5.13.0) | [6.2.0](https://github.com/prisma/orm/releases/tag/6.2.0) | +| `jsonProtocol` | [4.11.0](https://github.com/prisma/orm/releases/tag/4.11.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`extendedWhereUnique`](/orm/v6/reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) | [4.5.0](https://github.com/prisma/orm/releases/tag/4.5.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`fieldReference`](/orm/v6/reference/prisma-client-reference#compare-columns-in-the-same-table) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`clientExtensions`](/orm/v6/prisma-client/client-extensions) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`filteredRelationCount`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#filter-the-relation-count) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`tracing`](/orm/v6/prisma-client/observability-and-logging/opentelemetry-tracing) | [4.2.0](https://github.com/prisma/orm/releases/tag/4.2.0) | [6.1.0](https://github.com/prisma/orm/releases/tag/6.1.0) | +| [`orderByNulls`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last) | [4.1.0](https://github.com/prisma/orm/releases/tag/4.1.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`referentialIntegrity`](/orm/v6/prisma-schema/data-model/relations/relation-mode) | [3.1.1](https://github.com/prisma/orm/releases/tag/3.1.1) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0) | +| [`interactiveTransactions`](/orm/v6/prisma-client/queries/transactions#interactive-transactions) | [2.29.0](https://github.com/prisma/orm/releases/tag/2.29.0) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0)
with Prisma Accelerate [5.1.1](https://github.com/prisma/orm/releases/tag/5.1.1) | +| [`extendedIndexes`](/orm/v6/prisma-schema/data-model/indexes) | [3.5.0](https://github.com/prisma/orm/releases/tag/3.5.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`filterJson`](/orm/v6/prisma-client/special-fields-and-types/working-with-json-fields#filter-on-a-json-field-simple) | [2.23.0](https://github.com/prisma/orm/releases/tag/2.23.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`improvedQueryRaw`](/orm/v6/prisma-client/using-raw-sql/raw-queries#raw-query-type-mapping) | [3.14.0](https://github.com/prisma/orm/releases/tag/3.14.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`cockroachdb`](/orm/v6/overview/databases/cockroachdb) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0)
migrations in [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) | [3.14.0](https://github.com/prisma/orm/releases/tag/3.14.0) | +| [`mongodb`](/orm/v6/overview/databases/mongodb) | [2.27.0](https://github.com/prisma/orm/releases/tag/2.27.0)
introspection in [3.2.0](https://github.com/prisma/orm/releases/tag/3.2.0)
embedded docs in [3.4.0](https://github.com/prisma/orm/releases/tag/3.4.0)
raw queries in [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0)
filters/ordering in embedded docs in [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) | [3.12.0](https://github.com/prisma/orm/releases/tag/3.12.0) | +| [`microsoftSqlServer`](/orm/v6/overview/databases/sql-server) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`namedConstraints`](/orm/v6/prisma-schema/data-model/database-mapping#constraint-and-index-names) | [2.29.0](https://github.com/prisma/orm/releases/tag/2.29.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`referentialActions`](/orm/v6/prisma-schema/data-model/relations/referential-actions) | [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`orderByAggregateGroup`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#order-by-aggregate-group) | [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`orderByRelation`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relation) | [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0)
aggregates in [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`selectRelationCount`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#count-relations) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| `napi` | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`groupBy`](/orm/v6/reference/prisma-client-reference#groupby) | [2.14.0](https://github.com/prisma/orm/releases/tag/2.14.0) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | +| [`createMany`](/orm/v6/reference/prisma-client-reference#createmany) | [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | +| [`nativeTypes`](/orm/v6/prisma-schema/data-model/models#native-types-mapping) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) | +| [`uncheckedScalarInputs`](/orm/v6/prisma-client/queries/relation-queries#create-a-single-record-and-multiple-related-records) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) | +| [`transactionApi`](/orm/v6/prisma-client/queries/transactions#the-transaction-api) | [2.1.0](https://github.com/prisma/orm/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | +| [`connectOrCreate`](/orm/v6/reference/prisma-client-reference#connectorcreate) | [2.1.0](https://github.com/prisma/orm/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | +| [`atomicNumberOperations`](/orm/v6/reference/prisma-client-reference#atomic-number-operations) | [2.6.0](https://github.com/prisma/orm/releases/tag/2.6.0) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | +| [`insensitiveFilters` (PostgreSQL)](/orm/v6/prisma-client/queries/filtering-and-sorting#case-insensitive-filtering) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | [2.8.0](https://github.com/prisma/orm/releases/tag/2.8.0) | +| [`aggregateApi`](/orm/v6/prisma-client/queries/aggregation-grouping-summarizing#aggregate) | [2.2.0](https://github.com/prisma/orm/releases/tag/2.2.0) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | +| [`distinct`](/orm/v6/reference/prisma-client-reference#distinct) | [2.3.0](https://github.com/prisma/orm/releases/tag/2.3.0) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | diff --git a/apps/docs/content/docs/orm/v6/reference/preview-features/index.mdx b/apps/docs/content/docs/orm/v6/reference/preview-features/index.mdx index 48c693421b..e08019eb6a 100644 --- a/apps/docs/content/docs/orm/v6/reference/preview-features/index.mdx +++ b/apps/docs/content/docs/orm/v6/reference/preview-features/index.mdx @@ -7,7 +7,7 @@ metaTitle: Preview features metaDescription: Previews are typically available behind a feature flag or require some form of opt-in. --- -Some Prisma ORM features are released as [Previews](/orm/v6/more/releases#preview). [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). For information about available preview features and how to enable them, see: +Some Prisma ORM features are released as [Previews](/orm/v6/more/releases#preview). [Share your feedback on all Preview features on GitHub](https://github.com/prisma/orm/issues/3108). For information about available preview features and how to enable them, see: - [Prisma Client and Prisma schema preview features](/orm/v6/reference/preview-features/client-preview-features) - [Prisma CLI preview features](/orm/v6/reference/preview-features/cli-preview-features) diff --git a/apps/docs/content/docs/orm/v6/reference/prisma-cli-reference.mdx b/apps/docs/content/docs/orm/v6/reference/prisma-cli-reference.mdx index 431aef8ec3..958e0a07b8 100644 --- a/apps/docs/content/docs/orm/v6/reference/prisma-cli-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/prisma-cli-reference.mdx @@ -1499,7 +1499,7 @@ Other options: | Options | Required | Description | Notes | | :--------------- | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------ | :----------------------------------------------------------------------------- | | `--script` | No | Outputs a SQL script instead of the default human-readable summary | Not supported in MongoDB | -| `-o`, `--output` | No | Writes to a file instead of stdout | Available since [5.12.1](https://github.com/prisma/prisma/releases/tag/5.12.1) | +| `-o`, `--output` | No | Writes to a file instead of stdout | Available since [5.12.1](https://github.com/prisma/orm/releases/tag/5.12.1) | | `--exit-code` | No | Change the exit code behavior to signal if the diff is empty or not (Empty: 0, Error: 1, Not empty: 2). Default behavior is Success: 0, Error: 1. | | | `--config` | No | Custom path to your Prisma config file | | | `--help` | No | Displays the help message | | diff --git a/apps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdx b/apps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdx index 2f5cf3b1e3..df7333cee9 100644 --- a/apps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/prisma-client-reference.mdx @@ -564,7 +564,7 @@ Use model queries to perform CRUD operations on your models. See also: [CRUD](/o - By _ID_ - By a _unique_ attribute -`findUnique()` replaced `findOne` in version [2.12.0](https://github.com/prisma/prisma/releases/tag/2.12.0). +`findUnique()` replaced `findOne` in version [2.12.0](https://github.com/prisma/orm/releases/tag/2.12.0). #### Remarks @@ -1717,7 +1717,7 @@ See: [Using Raw SQL (`aggregateRaw()`)](/orm/v6/prisma-client/using-raw-sql/raw- #### Remarks - You cannot combine `select` and `include` on the same level. -- In [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later, you can [select a `_count` of relations](#select-a-_count-of-relations). +- In [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later, you can [select a `_count` of relations](#select-a-_count-of-relations). #### Examples @@ -1890,7 +1890,7 @@ const selectNameEmailNotPosts = Prisma.validator()({ #### Remarks -- In [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later, you can [`include` a `_count` of relations](#include-a-_count-of-relations) +- In [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later, you can [`include` a `_count` of relations](#include-a-_count-of-relations) #### Examples @@ -2215,11 +2215,11 @@ Sorts a list of records. See also: [Sorting](/orm/v6/prisma-client/queries/filte #### Remarks -- In [2.16.0](https://github.com/prisma/prisma/releases/2.16.0) and later, you can [order by relation fields](#sort-post-by-the-related-user-records-name) - for example, order posts by the author's name. +- In [2.16.0](https://github.com/prisma/orm/releases/2.16.0) and later, you can [order by relation fields](#sort-post-by-the-related-user-records-name) - for example, order posts by the author's name. -- In [3.5.0](https://github.com/prisma/prisma/releases/3.5.0) and later, in PostgreSQL you can [order by relevance](#sort-post-by-relevance-of-the-title). For details, see [Sort by relevance](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relevance-postgresql-and-mysql). +- In [3.5.0](https://github.com/prisma/orm/releases/3.5.0) and later, in PostgreSQL you can [order by relevance](#sort-post-by-relevance-of-the-title). For details, see [Sort by relevance](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relevance-postgresql-and-mysql). -- In [4.1.0](https://github.com/prisma/prisma/releases/4.1.0) and later, you can [sort `null` records first or last](#sort-post-by-the-related-user-records-name-with-null-records-first). For details, see [Sort with nulls first or last](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last). +- In [4.1.0](https://github.com/prisma/orm/releases/4.1.0) and later, you can [sort `null` records first or last](#sort-post-by-the-related-user-records-name-with-null-records-first). For details, see [Sort with nulls first or last](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last). #### Inputs for `sort` argument @@ -2941,7 +2941,7 @@ const user = await prisma.profile.create({ }); ``` -In [2.11.0](https://github.com/prisma/prisma/releases/2.11.0) and later, you can set the foreign key directly: +In [2.11.0](https://github.com/prisma/orm/releases/2.11.0) and later, you can set the foreign key directly: ```ts const user = await prisma.profile.create({ @@ -3154,8 +3154,8 @@ A nested `disconnect` query breaks the connection between a parent record and a - `disconnect` is only available if the relation is optional. - If the relationship you are attempting to disconnect does not exist: - - ([In 2.21.0 and later](https://github.com/prisma/prisma/releases/tag/2.21.0)), the operation does nothing - - (Before [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0)) Prisma Client throws an exception if the provided ID or unique identifier is not connected: + - ([In 2.21.0 and later](https://github.com/prisma/orm/releases/tag/2.21.0)), the operation does nothing + - (Before [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0)) Prisma Client throws an exception if the provided ID or unique identifier is not connected: ``` The records for relation `PostToUser` between the `User` and `Post` models are not connected. @@ -4175,7 +4175,7 @@ const setTags = await prisma.post.update({ ### `push` -`push` is available in version [2.20.0](https://github.com/prisma/prisma/releases/2.20.0) and later. Use `push` to add _one_ value or _multiple_ values to a scalar list field. +`push` is available in version [2.20.0](https://github.com/prisma/orm/releases/2.20.0) and later. Use `push` to add _one_ value or _multiple_ values to a scalar list field. #### Remarks @@ -4217,7 +4217,7 @@ const addTag = await prisma.post.update({ :::warning This method is available on MongoDB only in versions -[3.11.1](https://github.com/prisma/prisma/releases/tag/3.11.1) and later. +[3.11.1](https://github.com/prisma/orm/releases/tag/3.11.1) and later. ::: @@ -4248,9 +4248,9 @@ Scalar list filters allow you to filter by the contents of a list / array field. Available for: -- PostgreSQL in versions [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) and later -- CockroachDB in versions [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) and later -- MongoDB in versions [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) and later +- PostgreSQL in versions [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) and later +- CockroachDB in versions [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) and later +- MongoDB in versions [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) and later ::: @@ -4349,7 +4349,7 @@ const posts = await prisma.post.findMany({ :::warning This filter is available on MongoDB only in versions -[3.11.1](https://github.com/prisma/prisma/releases/tag/3.11.1) and later. +[3.11.1](https://github.com/prisma/orm/releases/tag/3.11.1) and later. ::: diff --git a/apps/docs/content/docs/orm/v6/reference/prisma-config-reference.mdx b/apps/docs/content/docs/orm/v6/reference/prisma-config-reference.mdx index 5a94dbf123..82cbb82d29 100644 --- a/apps/docs/content/docs/orm/v6/reference/prisma-config-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/prisma-config-reference.mdx @@ -416,7 +416,7 @@ export default { :::note -As of [Prisma ORM v6.11.0](https://github.com/prisma/prisma/releases/tag/6.11.0), the D1 adapter has been renamed from `PrismaD1HTTP` to `PrismaD1`. +As of [Prisma ORM v6.11.0](https://github.com/prisma/orm/releases/tag/6.11.0), the D1 adapter has been renamed from `PrismaD1HTTP` to `PrismaD1`. ::: diff --git a/apps/docs/content/docs/orm/v6/reference/prisma-schema-reference.mdx b/apps/docs/content/docs/orm/v6/reference/prisma-schema-reference.mdx index 41ddabe90a..319ef2998d 100644 --- a/apps/docs/content/docs/orm/v6/reference/prisma-schema-reference.mdx +++ b/apps/docs/content/docs/orm/v6/reference/prisma-schema-reference.mdx @@ -376,7 +376,7 @@ Defines a Prisma [model](/orm/v6/prisma-schema/data-model/models#defining-models - Model names must adhere to the following regular expression: `[A-Za-z][A-Za-z0-9_]*` - Model names must start with a letter and are typically spelled in [PascalCase](https://wiki.c2.com/?PascalCase) - Model names should use the singular form (for example, `User` instead of `user`, `users` or `Users`) -- Prisma ORM has a number of **reserved words** that are being used by Prisma ORM internally and therefore cannot be used as a model name. You can find the reserved words [here](https://github.com/prisma/prisma/blob/6.5.0/packages/client/src/generation/generateClient.ts#L556-L605) and [here](https://github.com/prisma/prisma-engines/blob/main/psl/parser-database/src/names/reserved_model_names.rs#L44). +- Prisma ORM has a number of **reserved words** that are being used by Prisma ORM internally and therefore cannot be used as a model name. You can find the reserved words [here](https://github.com/prisma/orm/blob/6.5.0/packages/client/src/generation/generateClient.ts#L556-L605) and [here](https://github.com/prisma/prisma-engines/blob/main/psl/parser-database/src/names/reserved_model_names.rs#L44). > **Note**: You can use the [`@@map` attribute](#map-1) to map a model (for example, `User`) to a table with a different name that does not match model naming conventions (for example, `users`). @@ -650,7 +650,7 @@ True or false value. ### `BigInt` -`BigInt` is available in version [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later. +`BigInt` is available in version [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later. #### Default type mappings @@ -708,7 +708,7 @@ True or false value. Floating point number. -> `Float` maps to `Double` in [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later - see [release notes](https://github.com/prisma/prisma/releases/tag/2.17.0) and [Video: Changes to the default mapping of Float in Prisma ORM 2.17.0](https://www.youtube.com/watch?v=OsuGP_xNHco&%3Bab_channel=Prisma) for more information about this change. +> `Float` maps to `Double` in [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later - see [release notes](https://github.com/prisma/orm/releases/tag/2.17.0) and [Video: Changes to the default mapping of Float in Prisma ORM 2.17.0](https://www.youtube.com/watch?v=OsuGP_xNHco&%3Bab_channel=Prisma) for more information about this change. #### Default type mappings @@ -964,7 +964,7 @@ Not supported ### `Bytes` -`Bytes` is available in version [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later. +`Bytes` is available in version [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later. #### Default type mappings @@ -1038,7 +1038,7 @@ The [MongoDB connector](/orm/v6/overview/databases/mongodb) does not support the ::: -The `Unsupported` type was introduced in [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and allows you to represent data types in the Prisma schema that are not supported by Prisma Client. Fields of type `Unsupported` can be created during Introspection with `prisma db pull` or written by hand, and created in the database with Prisma Migrate or `db push`. +The `Unsupported` type was introduced in [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and allows you to represent data types in the Prisma schema that are not supported by Prisma Client. Fields of type `Unsupported` can be created during Introspection with `prisma db pull` or written by hand, and created in the database with Prisma Migrate or `db push`. #### Remarks @@ -2561,7 +2561,7 @@ Automatically stores the time when a record was last updated. If you do not supp :::warning -In versions before [4.4.0](https://github.com/prisma/prisma/releases/tag/4.4.0), if you're also using [`now()`](/orm/v6/reference/prisma-schema-reference#now), the time might differ from the `@updatedAt` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. +In versions before [4.4.0](https://github.com/prisma/orm/releases/tag/4.4.0), if you're also using [`now()`](/orm/v6/reference/prisma-schema-reference#now), the time might differ from the `@updatedAt` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. ::: @@ -2612,7 +2612,7 @@ Add `@ignore` to a field that you want to exclude from Prisma Client (for exampl #### Remarks -- In [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later, Prisma ORM automatically adds `@ignore` to fields that _refer to_ invalid models when you introspect. +- In [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later, Prisma ORM automatically adds `@ignore` to fields that _refer to_ invalid models when you introspect. #### Examples @@ -2632,7 +2632,7 @@ Add `@@ignore` to a model that you want to exclude from Prisma Client (for examp #### Remarks -- In [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later, Prisma ORM adds `@@ignore` to an invalid model. (It also adds [`@ignore`](#ignore) to relations pointing to such a model) +- In [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later, Prisma ORM adds `@@ignore` to an invalid model. (It also adds [`@ignore`](#ignore) to relations pointing to such a model) #### Examples @@ -3065,7 +3065,7 @@ Set a timestamp of the time when a record is created. :::warning -In versions before [4.4.0](https://github.com/prisma/prisma/releases/tag/4.4.0), if you're also using [`@updatedAt`](/orm/v6/reference/prisma-schema-reference#updatedat), the time might differ from the `now()` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. +In versions before [4.4.0](https://github.com/prisma/orm/releases/tag/4.4.0), if you're also using [`@updatedAt`](/orm/v6/reference/prisma-schema-reference#updatedat), the time might differ from the `now()` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. ::: @@ -3111,8 +3111,8 @@ Represents **default values** that cannot be expressed in the Prisma schema (suc ##### Relational databases - Compatible with any scalar type -- Can not be an empty string `dbgenerated("")` in [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0) and later -- Accepts a `String` value in [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later, which allows you to: +- Can not be an empty string `dbgenerated("")` in [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0) and later +- Accepts a `String` value in [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and later, which allows you to: - [Set default values for `Unsupported` types](#set-default-value-for-unsupported-type) - [Override default value behavior for supported types](#override-default-value-behavior-for-supported-types) diff --git a/apps/docs/content/docs/orm/v6/reference/supported-databases.mdx b/apps/docs/content/docs/orm/v6/reference/supported-databases.mdx index 23d218d653..8598966336 100644 --- a/apps/docs/content/docs/orm/v6/reference/supported-databases.mdx +++ b/apps/docs/content/docs/orm/v6/reference/supported-databases.mdx @@ -55,4 +55,4 @@ Note that a fixed version of SQLite is shipped with every Prisma ORM release. | Cloudflare D1 (Preview) | \* | | Aiven (MySQL & Postgres) | \* | -¹ This does not include support for [Data API for Aurora Serverless](https://github.com/prisma/prisma/issues/1964). +¹ This does not include support for [Data API for Aurora Serverless](https://github.com/prisma/orm/issues/1964). diff --git a/apps/docs/content/docs/orm/v7/core-concepts/supported-databases/database-drivers.mdx b/apps/docs/content/docs/orm/v7/core-concepts/supported-databases/database-drivers.mdx index f1ab2bce32..2f54b4c9c1 100644 --- a/apps/docs/content/docs/orm/v7/core-concepts/supported-databases/database-drivers.mdx +++ b/apps/docs/content/docs/orm/v7/core-concepts/supported-databases/database-drivers.mdx @@ -73,7 +73,7 @@ Refer to the following pages to learn more about how to use the specific driver ### New driver adapters API in v6.6.0 -In [v6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0), we introduced a simplified version for instantiating Prisma Client when using driver adapters. You now don't need to create an instance of the driver/client to pass to a driver adapter, instead you create the driver adapter directly (and pass the driver's options to it if needed). +In [v6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0), we introduced a simplified version for instantiating Prisma Client when using driver adapters. You now don't need to create an instance of the driver/client to pass to a driver adapter, instead you create the driver adapter directly (and pass the driver's options to it if needed). Here is an example using the `@prisma/adapter-libsql` adapter: diff --git a/apps/docs/content/docs/orm/v7/index.mdx b/apps/docs/content/docs/orm/v7/index.mdx index 99f91346d9..eca9993318 100644 --- a/apps/docs/content/docs/orm/v7/index.mdx +++ b/apps/docs/content/docs/orm/v7/index.mdx @@ -6,7 +6,7 @@ metaTitle: What is Prisma ORM? (Overview) metaDescription: 'Prisma ORM is a next-generation Node.js and TypeScript ORM that provides type-safe database access, migrations, and a visual data editor.' --- -Prisma ORM is [open-source](https://github.com/prisma/prisma) and consists of: +Prisma ORM is [open-source](https://github.com/prisma/orm) and consists of: - [**Prisma Client**](/orm/v7/prisma-client): Auto-generated, type-safe **ORM interface** - [**Prisma Migrate**](/orm/v7/prisma-migrate): Database migration system diff --git a/apps/docs/content/docs/orm/v7/more/releases.mdx b/apps/docs/content/docs/orm/v7/more/releases.mdx index 2a5979fdba..7f700eca62 100644 --- a/apps/docs/content/docs/orm/v7/more/releases.mdx +++ b/apps/docs/content/docs/orm/v7/more/releases.mdx @@ -12,13 +12,13 @@ This page explains the release process of Prisma ORM, how it's versioned and how Prisma ORM releases typically happen every two weeks. Note that this is _not_ a hard rule – releases might be postponed for internal reasons. -[Check out all the releases notes in GitHub](https://github.com/prisma/prisma/releases). +[Check out all the releases notes in GitHub](https://github.com/prisma/orm/releases). ## Product maturity levels A release can include products or features at different maturity levels. Maturity level describes a product or feature's completeness and what users can expect in terms of breaking changes. -> **Note**: As of version [2.13.0](https://github.com/prisma/prisma/releases/2.13.0), 'Experimental' is no longer part of the product maturity scale. +> **Note**: As of version [2.13.0](https://github.com/prisma/orm/releases/2.13.0), 'Experimental' is no longer part of the product maturity scale. ### Early Access diff --git a/apps/docs/content/docs/orm/v7/more/troubleshooting/bundler-issues.mdx b/apps/docs/content/docs/orm/v7/more/troubleshooting/bundler-issues.mdx index 4df1d972a1..a7cbbe140a 100644 --- a/apps/docs/content/docs/orm/v7/more/troubleshooting/bundler-issues.mdx +++ b/apps/docs/content/docs/orm/v7/more/troubleshooting/bundler-issues.mdx @@ -26,4 +26,4 @@ Add your Prisma query engine binary path to the `pkg/assets` section of your `pa } ``` -See [this Github issue](https://github.com/prisma/prisma/issues/8449) for further discussion. +See [this Github issue](https://github.com/prisma/orm/issues/8449) for further discussion. diff --git a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/result.mdx b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/result.mdx index 5e66673c6e..5385a99c8f 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/result.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/result.mdx @@ -196,7 +196,7 @@ In this case, omitting both `password` and `sanitizedPassword` will exclude both ## Limitation -As of now, Prisma Client's result extension component does not support relation fields. This means that you cannot create custom fields or methods based on related models or fields in a relational relationship (e.g., user.posts, post.author). The needs parameter can only reference scalar fields within the same model. Follow [issue #20091 on GitHub](https://github.com/prisma/prisma/issues/20091). +As of now, Prisma Client's result extension component does not support relation fields. This means that you cannot create custom fields or methods based on related models or fields in a relational relationship (e.g., user.posts, post.author). The needs parameter can only reference scalar fields within the same model. Follow [issue #20091 on GitHub](https://github.com/prisma/orm/issues/20091). ```ts const prisma = new PrismaClient().$extends({ diff --git a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/index.mdx b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/index.mdx index c1812ad89c..e0a7e559b7 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/index.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/index.mdx @@ -94,7 +94,7 @@ There's currently a limitation for extensions that reference a `PrismaClient` an If you trigger the extension from inside a [transaction](/orm/v7/prisma-client/queries/transactions) (interactive or batched), the extension code will issue the queries in a new connection and ignore the current transaction context. -Learn more in this issue on GitHub: [Client extensions that require use of a client-level method silently ignore transactions](https://github.com/prisma/prisma/issues/20678). +Learn more in this issue on GitHub: [Client extensions that require use of a client-level method silently ignore transactions](https://github.com/prisma/orm/issues/20678). ::: diff --git a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/overview.mdx b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/overview.mdx index 691dfaf3e0..8ff08afe68 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/overview.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/overview.mdx @@ -25,7 +25,7 @@ Here is a brief overview of all the edge function providers that are currently s | Vercel Edge Middleware | ✅ (Preview; only compatible drivers) | ✅ | | Cloudflare Workers | ✅ (Preview; only compatible drivers) | ✅ | | Cloudflare Pages | ✅ (Preview; only compatible drivers) | ✅ | -| Deno Deploy | [Not yet](https://github.com/prisma/prisma/issues/2452) | ✅ | +| Deno Deploy | [Not yet](https://github.com/prisma/orm/issues/2452) | ✅ | Deploying edge functions that use Prisma ORM on Cloudflare and Vercel is currently in [Preview](/orm/v7/more/releases#preview). diff --git a/apps/docs/content/docs/orm/v7/prisma-client/queries/aggregation-grouping-summarizing.mdx b/apps/docs/content/docs/orm/v7/prisma-client/queries/aggregation-grouping-summarizing.mdx index 61caf802db..b9ec2b9206 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/queries/aggregation-grouping-summarizing.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/queries/aggregation-grouping-summarizing.mdx @@ -418,7 +418,7 @@ await prisma.user.findMany({ ### Count non-`null` field values -In [2.15.0](https://github.com/prisma/prisma/releases/2.15.0) and later, you can count all records as well as all instances of non-`null` field values. The following query returns a count of: +In [2.15.0](https://github.com/prisma/orm/releases/2.15.0) and later, you can count all records as well as all instances of non-`null` field values. The following query returns a count of: - All `User` records (`_all`) - All non-`null` `name` values (not distinct values, just values that are not `null`) diff --git a/apps/docs/content/docs/orm/v7/prisma-client/queries/relation-queries.mdx b/apps/docs/content/docs/orm/v7/prisma-client/queries/relation-queries.mdx index b897469540..5bf9118554 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/queries/relation-queries.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/queries/relation-queries.mdx @@ -322,7 +322,7 @@ const user = await prisma.user.findFirst({ ## Relation count -In [3.0.1](https://github.com/prisma/prisma/releases/3.0.1) and later, you can [`include` or `select` a count of relations](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields - for example, a user's post count. +In [3.0.1](https://github.com/prisma/orm/releases/3.0.1) and later, you can [`include` or `select` a count of relations](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#count-relations) alongside fields - for example, a user's post count. ```ts const relationCount = await prisma.user.findMany({ diff --git a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/index.mdx b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/index.mdx index 0df31dd909..502435cdff 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/index.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/index.mdx @@ -40,7 +40,7 @@ const newTypes = await prisma.sample.create({ :::warning -The use of the `Decimal` field [is not currently supported in MongoDB](https://github.com/prisma/prisma/issues/12637). +The use of the `Decimal` field [is not currently supported in MongoDB](https://github.com/prisma/orm/issues/12637). ::: @@ -95,7 +95,7 @@ const newTypes = await prisma.sample.create({ :::note -There currently is a [bug](https://github.com/prisma/prisma/issues/9516) that doesn't allow you to pass in `DateTime` values as strings and produces a runtime error when you do. `DateTime` values need to be passed as [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) objects (i.e. `new Date('2024-12-04')` instead of `'2024-12-04'`). +There currently is a [bug](https://github.com/prisma/orm/issues/9516) that doesn't allow you to pass in `DateTime` values as strings and produces a runtime error when you do. `DateTime` values need to be passed as [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) objects (i.e. `new Date('2024-12-04')` instead of `'2024-12-04'`). ::: diff --git a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/null-and-undefined.mdx b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/null-and-undefined.mdx index 1bc0c818f1..4814d56fe7 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/null-and-undefined.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/null-and-undefined.mdx @@ -115,7 +115,7 @@ Learn more about `exactOptionalPropertyTypes` in the [TypeScript documentation]( ### Feedback -As always, we welcome your feedback on this feature. Please share your thoughts and suggestions in the [GitHub discussion for this Preview feature](https://github.com/prisma/prisma/discussions/25271). +As always, we welcome your feedback on this feature. Please share your thoughts and suggestions in the [GitHub discussion for this Preview feature](https://github.com/prisma/orm/discussions/25271). ## current behavior diff --git a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields.mdx b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields.mdx index 79ca947be0..868f02a3d1 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields.mdx @@ -910,7 +910,7 @@ For a complete guide on configuration, monorepo setup, and other advanced featur ### Can you select a subset of JSON key/values to return? -No - it is not yet possible to [select which JSON elements to return](https://github.com/prisma/prisma/issues/2431). Prisma Client returns the entire JSON object. +No - it is not yet possible to [select which JSON elements to return](https://github.com/prisma/orm/issues/2431). Prisma Client returns the entire JSON object. ### Can you filter on the presence of a specific key? @@ -922,7 +922,7 @@ Yes - you can use the `mode: 'insensitive'` option with string filters like `str ### Can you sort an object property within a JSON value? -No, [sorting object properties within a JSON value](https://github.com/prisma/prisma/issues/10346) (order-by-prop) is not currently supported. +No, [sorting object properties within a JSON value](https://github.com/prisma/orm/issues/10346) (order-by-prop) is not currently supported. ### How to set a default value for JSON fields? diff --git a/apps/docs/content/docs/orm/v7/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx b/apps/docs/content/docs/orm/v7/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx index 5d1662ea1f..38f9f35849 100644 --- a/apps/docs/content/docs/orm/v7/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-migrate/understanding-prisma-migrate/limitations-and-known-issues.mdx @@ -14,7 +14,7 @@ Prisma Migrate does not currently support the MongoDB connector. Prisma Migrate generates SQL files that are specific to your provider. This means that you cannot use the same migration files for PostgreSQL in production and SQLite in development, because the syntax in the migrations will be incompatible. -As of [2.15.0](https://github.com/prisma/prisma/releases/2.15.0), Prisma Migrate detects when the migrations do not match the configured provider and prints a helpful error message. For example, if your migrations are for a PostgreSQL database but your `provider` is set to `mysql`: +As of [2.15.0](https://github.com/prisma/orm/releases/2.15.0), Prisma Migrate detects when the migrations do not match the configured provider and prints a helpful error message. For example, if your migrations are for a PostgreSQL database but your `provider` is set to `mysql`: ``` Error: P3014 diff --git a/apps/docs/content/docs/orm/v7/prisma-migrate/workflows/patching-and-hotfixing.mdx b/apps/docs/content/docs/orm/v7/prisma-migrate/workflows/patching-and-hotfixing.mdx index 2c883674d6..4d59ac7776 100644 --- a/apps/docs/content/docs/orm/v7/prisma-migrate/workflows/patching-and-hotfixing.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-migrate/workflows/patching-and-hotfixing.mdx @@ -249,4 +249,4 @@ Error: undefined: Database error Error querying the database: db error: ERROR: prepared statement "s0" already exists ``` -See [Prisma Migrate and PgBouncer workaround](/orm/v7/prisma-client/setup-and-configuration/databases-connections/pgbouncer) for further information and a workaround. Follow [GitHub issue #6485](https://github.com/prisma/prisma/issues/6485) for updates. +See [Prisma Migrate and PgBouncer workaround](/orm/v7/prisma-client/setup-and-configuration/databases-connections/pgbouncer) for further information and a workaround. Follow [GitHub issue #6485](https://github.com/prisma/orm/issues/6485) for updates. diff --git a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/indexes.mdx b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/indexes.mdx index 4aa0a1f3d0..f3e0f9c1ce 100644 --- a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/indexes.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/indexes.mdx @@ -662,7 +662,7 @@ The `fullTextIndex` preview feature provides support for introspection and migra :::warning -For now we do not enable the full text search commands in Prisma Client for MongoDB; the progress can be followed in the [MongoDB](https://github.com/prisma/prisma/issues/9413) issue. +For now we do not enable the full text search commands in Prisma Client for MongoDB; the progress can be followed in the [MongoDB](https://github.com/prisma/orm/issues/9413) issue. ::: diff --git a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/relations/referential-actions.mdx b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/relations/referential-actions.mdx index 44e8d3dcd8..e75fccdeb4 100644 --- a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/relations/referential-actions.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/relations/referential-actions.mdx @@ -63,7 +63,7 @@ If you do not specify a referential action, Prisma ORM uses the following defaul The following caveats apply: - Referential actions are **not** supported on [implicit many-to-many relations](/orm/v7/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations). To use referential actions, you must define an explicit many-to-many relation and define your referential actions on the [join table](/orm/v7/prisma-schema/data-model/relations/troubleshooting-relations#how-to-use-a-relation-table-with-a-many-to-many-relationship). -- Certain combinations of referential actions and required/optional relations are incompatible. For example, using `SetNull` on a required relation will lead to database errors when deleting referenced records because the non-nullable constraint would be violated. See [this GitHub issue](https://github.com/prisma/prisma/issues/7909) for more information. +- Certain combinations of referential actions and required/optional relations are incompatible. For example, using `SetNull` on a required relation will lead to database errors when deleting referenced records because the non-nullable constraint would be violated. See [this GitHub issue](https://github.com/prisma/orm/issues/7909) for more information. ## Types of referential actions diff --git a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/views.mdx b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/views.mdx index 2aa3ef5a13..66f8d0d2e0 100644 --- a/apps/docs/content/docs/orm/v7/prisma-schema/data-model/views.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-schema/data-model/views.mdx @@ -18,7 +18,7 @@ The `views` preview feature allows you to represent views in your Prisma schema :::warning -Support for views is currently a [Preview](/orm/v7/more/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag.

For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/prisma/issues/17335). +Support for views is currently a [Preview](/orm/v7/more/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag.

For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/orm/issues/17335). ::: @@ -34,7 +34,7 @@ generator client { } ``` -Please leave feedback about this preview feature in our dedicated preview feature [feedback issue](https://github.com/prisma/prisma/issues/17335) for `views`. +Please leave feedback about this preview feature in our dedicated preview feature [feedback issue](https://github.com/prisma/orm/issues/17335) for `views`. ## Create a view in the underlying database @@ -279,7 +279,7 @@ Materialized views persist the result of the view query for faster access and on Currently, Prisma ORM does not support materialized views. However, when you [manually create a view](#create-a-view-in-the-underlying-database), you can also create a materialized view with the corresponding command in the underlying database. You can then use Prisma Client's [TypedSQL functionality](/orm/v7/prisma-client/using-raw-sql) to execute the command and refresh the view manually. -In the future Prisma Client might support marking individual views as materialized and add a Prisma Client method to refresh the materialized view. Please comment on our [`views` feedback issue](https://github.com/prisma/prisma/issues/17335) with your use case. +In the future Prisma Client might support marking individual views as materialized and add a Prisma Client method to refresh the materialized view. Please comment on our [`views` feedback issue](https://github.com/prisma/orm/issues/17335) with your use case. ## Limitations diff --git a/apps/docs/content/docs/orm/v7/prisma-schema/introspection.mdx b/apps/docs/content/docs/orm/v7/prisma-schema/introspection.mdx index 40629521d0..ab2c4b4c4e 100644 --- a/apps/docs/content/docs/orm/v7/prisma-schema/introspection.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-schema/introspection.mdx @@ -338,7 +338,7 @@ Use cases include: ## Introspecting only a subset of your database schema -Introspecting only a subset of your database schema is [not yet officially supported](https://github.com/prisma/prisma/issues/807) by Prisma ORM. +Introspecting only a subset of your database schema is [not yet officially supported](https://github.com/prisma/orm/issues/807) by Prisma ORM. However, you can achieve this by creating a new database user that only has access to the tables which you'd like to see represented in your Prisma schema, and then perform the introspection using that user. The introspection will then only include the tables the new user has access to. @@ -352,18 +352,18 @@ For these features, the Prisma CLI will surface detect usage of the feature in y The `prisma db pull` command will surface the following unsupported features: -- [Partitioned tables](https://github.com/prisma/prisma/issues/1708) -- [PostgreSQL Row Level Security](https://github.com/prisma/prisma/issues/12735) -- [Index sort order, `NULLS FIRST` / `NULLS LAST`](https://github.com/prisma/prisma/issues/15466) -- [CockroachDB row-level TTL](https://github.com/prisma/prisma/issues/13982) -- [Comments](https://github.com/prisma/prisma/issues/8703) -- [PostgreSQL deferred constraints](https://github.com/prisma/prisma/issues/8807) -- [Check Constraints](https://github.com/prisma/prisma/issues/3388) (MySQL + PostgreSQL) -- [Exclusion Constraints](https://github.com/prisma/prisma/issues/17514) -- [MongoDB $jsonSchema](https://github.com/prisma/prisma/issues/8135) -- [Expression indexes](https://github.com/prisma/prisma/issues/2504) - -You can find the list of features we intend to support on [GitHub (labeled with `topic:database-functionality`)](https://github.com/prisma/prisma/issues?q=is%3Aopen+label%3A%22topic%3A+database-functionality%22+label%3Ateam%2Fschema+sort%3Aupdated-desc+). +- [Partitioned tables](https://github.com/prisma/orm/issues/1708) +- [PostgreSQL Row Level Security](https://github.com/prisma/orm/issues/12735) +- [Index sort order, `NULLS FIRST` / `NULLS LAST`](https://github.com/prisma/orm/issues/15466) +- [CockroachDB row-level TTL](https://github.com/prisma/orm/issues/13982) +- [Comments](https://github.com/prisma/orm/issues/8703) +- [PostgreSQL deferred constraints](https://github.com/prisma/orm/issues/8807) +- [Check Constraints](https://github.com/prisma/orm/issues/3388) (MySQL + PostgreSQL) +- [Exclusion Constraints](https://github.com/prisma/orm/issues/17514) +- [MongoDB $jsonSchema](https://github.com/prisma/orm/issues/8135) +- [Expression indexes](https://github.com/prisma/orm/issues/2504) + +You can find the list of features we intend to support on [GitHub (labeled with `topic:database-functionality`)](https://github.com/prisma/orm/issues?q=is%3Aopen+label%3A%22topic%3A+database-functionality%22+label%3Ateam%2Fschema+sort%3Aupdated-desc+). ### Workaround for introspection warnings for unsupported features diff --git a/apps/docs/content/docs/orm/v7/reference/error-reference.mdx b/apps/docs/content/docs/orm/v7/reference/error-reference.mdx index a4410db93b..3ac17f9b07 100644 --- a/apps/docs/content/docs/orm/v7/reference/error-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/error-reference.mdx @@ -336,7 +336,7 @@ In Prisma ORM v7, pool size and timeout are configured per [driver adapter](/orm :::warning -The Schema Engine was previously called Migration Engine. This change was introduced in version [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0). +The Schema Engine was previously called Migration Engine. This change was introduced in version [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0). ::: @@ -394,7 +394,7 @@ The Schema Engine was previously called Migration Engine. This change was introd #### `P3013` -"Datasource provider arrays are no longer supported in migrate. Please change your datasource to use a single provider. Read more at [https://pris.ly/multi-provider-deprecation](https://pris.ly/multi-provider-deprecation)" +"Datasource provider arrays are no longer supported in migrate. Please change your datasource to use a single provider. Read more at [https://pris.ly/multi-provider-deprecation](https://github.com/prisma/orm/issues/3834)" #### `P3014` diff --git a/apps/docs/content/docs/orm/v7/reference/preview-features/cli-preview-features.mdx b/apps/docs/content/docs/orm/v7/reference/preview-features/cli-preview-features.mdx index 8d3c293c0e..476a659996 100644 --- a/apps/docs/content/docs/orm/v7/reference/preview-features/cli-preview-features.mdx +++ b/apps/docs/content/docs/orm/v7/reference/preview-features/cli-preview-features.mdx @@ -20,7 +20,7 @@ In the list below, you can find a history of Prisma CLI features that were in Pr | Features | Released in Preview | Released in general availability | | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------- | -| [`prisma migrate diff`](/orm/v7/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/prisma/releases/tag/3.13.0) | -| [`prisma db execute`](/orm/v7/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/prisma/releases/tag/3.13.0) | -| [`prisma db push`](/orm/v7/prisma-migrate/workflows/prototyping-your-schema) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | [2.22.0](https://github.com/prisma/prisma/releases/tag/2.22.0) | -| [`prisma migrate`](/orm/v7/prisma-migrate) | [2.13.0](https://github.com/prisma/prisma/releases/tag/2.13.0) | [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0) | +| [`prisma migrate diff`](/orm/v7/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/orm/releases/tag/3.13.0) | +| [`prisma db execute`](/orm/v7/prisma-migrate/workflows/patching-and-hotfixing#fixing-failed-migrations-with-migrate-diff-and-db-execute) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0) | [3.13.0](https://github.com/prisma/orm/releases/tag/3.13.0) | +| [`prisma db push`](/orm/v7/prisma-migrate/workflows/prototyping-your-schema) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | [2.22.0](https://github.com/prisma/orm/releases/tag/2.22.0) | +| [`prisma migrate`](/orm/v7/prisma-migrate) | [2.13.0](https://github.com/prisma/orm/releases/tag/2.13.0) | [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0) | diff --git a/apps/docs/content/docs/orm/v7/reference/preview-features/client-preview-features.mdx b/apps/docs/content/docs/orm/v7/reference/preview-features/client-preview-features.mdx index 3721ee9202..870b79c11b 100644 --- a/apps/docs/content/docs/orm/v7/reference/preview-features/client-preview-features.mdx +++ b/apps/docs/content/docs/orm/v7/reference/preview-features/client-preview-features.mdx @@ -16,16 +16,16 @@ The following [Preview](/orm/v7/more/releases#preview) feature flags are availab | Feature | Released into Preview | Feedback issue | | ----------------------------------------------------------------------- | :------------------------------------------------------------- | :-------------------------------------------------------------------: | -| [`views`](/orm/v7/prisma-schema/data-model/views) | [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0) | [Submit feedback](https://github.com/prisma/prisma/issues/17335) | -| `relationJoins` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22288) | -| `nativeDistinct` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22287) | -| `typedSql` | [5.19.0](https://github.com/prisma/prisma/releases/tag/5.19.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/25106) | -| `strictUndefinedChecks` | [5.20.0](https://github.com/prisma/prisma/releases/tag/5.20.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/25271) | -| [`fullTextSearchPostgres`](/orm/v6/prisma-client/queries/full-text-search) | [6.0.0](https://github.com/prisma/prisma/releases/tag/6.0.0) | [Submit feedback](https://github.com/prisma/prisma/issues/25773) | -| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/prisma/issues/) | -| [`partialIndexes`](/orm/v7/prisma-schema/data-model/indexes) | [7.4.0](https://pris.ly/release/7.4.0) | [Submit feedback](https://github.com/prisma/prisma/issues/6974) | +| [`views`](/orm/v7/prisma-schema/data-model/views) | [4.9.0](https://github.com/prisma/orm/releases/tag/4.9.0) | [Submit feedback](https://github.com/prisma/orm/issues/17335) | +| `relationJoins` | [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/orm/discussions/22288) | +| `nativeDistinct` | [5.7.0](https://github.com/prisma/orm/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/orm/discussions/22287) | +| `typedSql` | [5.19.0](https://github.com/prisma/orm/releases/tag/5.19.0) | [Submit feedback](https://github.com/prisma/orm/discussions/25106) | +| `strictUndefinedChecks` | [5.20.0](https://github.com/prisma/orm/releases/tag/5.20.0) | [Submit feedback](https://github.com/prisma/orm/discussions/25271) | +| [`fullTextSearchPostgres`](/orm/v6/prisma-client/queries/full-text-search) | [6.0.0](https://github.com/prisma/orm/releases/tag/6.0.0) | [Submit feedback](https://github.com/prisma/orm/issues/25773) | +| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/orm/issues/) | +| [`partialIndexes`](/orm/v7/prisma-schema/data-model/indexes) | [7.4.0](https://pris.ly/release/7.4.0) | [Submit feedback](https://github.com/prisma/orm/issues/6974) | -To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). +To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/orm/issues/3108). ## Enabling a Prisma Client Preview feature @@ -55,38 +55,38 @@ In the list below, you can find a history of Prisma Client and Prisma schema fea | Feature | Released into Preview | Released into General Availability | | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`driverAdapters`](/orm/v7/core-concepts/supported-databases/database-drivers#driver-adapters) | [5.4.0](https://github.com/prisma/prisma/releases/tag/5.4.0) | [6.16.0](https://github.com/prisma/prisma/releases/tag/6.16.0) | -| [`multiSchema`](/orm/v7/prisma-schema/data-model/multi-schema) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [6.13.0](https://github.com/prisma/prisma/releases/tag/6.13.0) | -| [`prismaSchemaFolder`](/orm/v7/prisma-schema/overview/location#multi-file-prisma-schema) | [5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0) | [6.7.0](https://pris.ly/release/6.7.0) | -| `omitApi` | [5.13.0](https://github.com/prisma/prisma/releases/tag/5.13.0) | [6.2.0](https://github.com/prisma/prisma/releases/tag/6.2.0) | -| `jsonProtocol` | [4.11.0](https://github.com/prisma/prisma/releases/tag/4.11.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`extendedWhereUnique`](/orm/v7/reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) | [4.5.0](https://github.com/prisma/prisma/releases/tag/4.5.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`fieldReference`](/orm/v7/reference/prisma-client-reference#compare-columns-in-the-same-table) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [5.0.0](https://github.com/prisma/prisma/releases/tag/5.0.0) | -| [`clientExtensions`](/orm/v7/prisma-client/client-extensions) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`filteredRelationCount`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#filter-the-relation-count) | [4.3.0](https://github.com/prisma/prisma/releases/tag/4.3.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`tracing`](/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing) | [4.2.0](https://github.com/prisma/prisma/releases/tag/4.2.0) | [6.1.0](https://github.com/prisma/prisma/releases/tag/6.1.0) | -| [`orderByNulls`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last) | [4.1.0](https://github.com/prisma/prisma/releases/tag/4.1.0) | [4.16.0](https://github.com/prisma/prisma/releases/tag/4.16.0) | -| [`referentialIntegrity`](/orm/v7/prisma-schema/data-model/relations/relation-mode) | [3.1.1](https://github.com/prisma/prisma/releases/tag/3.1.1) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0) | -| [`interactiveTransactions`](/orm/v7/prisma-client/queries/transactions#interactive-transactions) | [2.29.0](https://github.com/prisma/prisma/releases/tag/2.29.0) | [4.7.0](https://github.com/prisma/prisma/releases/tag/4.7.0)
with Prisma Accelerate [5.1.1](https://github.com/prisma/prisma/releases/tag/5.1.1) | -| [`extendedIndexes`](/orm/v7/prisma-schema/data-model/indexes) | [3.5.0](https://github.com/prisma/prisma/releases/tag/3.5.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`filterJson`](/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields#filter-on-a-json-field-simple) | [2.23.0](https://github.com/prisma/prisma/releases/tag/2.23.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`improvedQueryRaw`](/orm/v7/prisma-client/using-raw-sql/raw-queries#raw-query-type-mapping) | [3.14.0](https://github.com/prisma/prisma/releases/tag/3.14.0) | [4.0.0](https://github.com/prisma/prisma/releases/tag/4.0.0) | -| [`cockroachdb`](/orm/v7/core-concepts/supported-databases/postgresql#cockroachdb) | [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0)
migrations in [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) | [3.14.0](https://github.com/prisma/prisma/releases/tag/3.14.0) | -| [`mongodb`](/orm/v7/core-concepts/supported-databases/mongodb) | [2.27.0](https://github.com/prisma/prisma/releases/tag/2.27.0)
introspection in [3.2.0](https://github.com/prisma/prisma/releases/tag/3.2.0)
embedded docs in [3.4.0](https://github.com/prisma/prisma/releases/tag/3.4.0)
raw queries in [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0)
filters/ordering in embedded docs in [3.11.0](https://github.com/prisma/prisma/releases/tag/3.11.0) | [3.12.0](https://github.com/prisma/prisma/releases/tag/3.12.0) | -| [`microsoftSqlServer`](/orm/v7/core-concepts/supported-databases/sql-server) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`namedConstraints`](/orm/v7/prisma-schema/data-model/database-mapping#constraint-and-index-names) | [2.29.0](https://github.com/prisma/prisma/releases/tag/2.29.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`referentialActions`](/orm/v7/prisma-schema/data-model/relations/referential-actions) | [2.26.0](https://github.com/prisma/prisma/releases/tag/2.26.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`orderByAggregateGroup`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#order-by-aggregate-group) | [2.21.0](https://github.com/prisma/prisma/releases/tag/2.21.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`orderByRelation`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relation) | [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0)
aggregates in [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`selectRelationCount`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#count-relations) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| `napi` | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/prisma/releases/tag/3.0.1) | -| [`groupBy`](/orm/v7/reference/prisma-client-reference#groupby) | [2.14.0](https://github.com/prisma/prisma/releases/tag/2.14.0) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | -| [`createMany`](/orm/v7/reference/prisma-client-reference#createmany) | [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0) | [2.20.0](https://github.com/prisma/prisma/releases/tag/2.20.0) | -| [`nativeTypes`](/orm/v7/prisma-schema/data-model/models#native-types-mapping) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) | -| [`uncheckedScalarInputs`](/orm/v7/prisma-client/queries/relation-queries#create-a-single-record-and-multiple-related-records) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | [2.15.0](https://github.com/prisma/prisma/releases/tag/2.15.0) | -| [`transactionApi`](/orm/v7/prisma-client/queries/transactions#the-transaction-api) | [2.1.0](https://github.com/prisma/prisma/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | -| [`connectOrCreate`](/orm/v7/reference/prisma-client-reference#connectorcreate) | [2.1.0](https://github.com/prisma/prisma/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/prisma/releases/tag/2.11.0) | -| [`atomicNumberOperations`](/orm/v7/reference/prisma-client-reference#atomic-number-operations) | [2.6.0](https://github.com/prisma/prisma/releases/tag/2.6.0) | [2.10.0](https://github.com/prisma/prisma/releases/tag/2.10.0) | -| [`insensitiveFilters` (PostgreSQL)](/orm/v6/prisma-client/queries/filtering-and-sorting#case-insensitive-filtering) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | [2.8.0](https://github.com/prisma/prisma/releases/tag/2.8.0) | -| [`aggregateApi`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#aggregate) | [2.2.0](https://github.com/prisma/prisma/releases/tag/2.2.0) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | -| [`distinct`](/orm/v7/reference/prisma-client-reference#distinct) | [2.3.0](https://github.com/prisma/prisma/releases/tag/2.3.0) | [2.5.0](https://github.com/prisma/prisma/releases/tag/2.5.0) | +| [`driverAdapters`](/orm/v7/core-concepts/supported-databases/database-drivers#driver-adapters) | [5.4.0](https://github.com/prisma/orm/releases/tag/5.4.0) | [6.16.0](https://github.com/prisma/orm/releases/tag/6.16.0) | +| [`multiSchema`](/orm/v7/prisma-schema/data-model/multi-schema) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [6.13.0](https://github.com/prisma/orm/releases/tag/6.13.0) | +| [`prismaSchemaFolder`](/orm/v7/prisma-schema/overview/location#multi-file-prisma-schema) | [5.15.0](https://github.com/prisma/orm/releases/tag/5.15.0) | [6.7.0](https://pris.ly/release/6.7.0) | +| `omitApi` | [5.13.0](https://github.com/prisma/orm/releases/tag/5.13.0) | [6.2.0](https://github.com/prisma/orm/releases/tag/6.2.0) | +| `jsonProtocol` | [4.11.0](https://github.com/prisma/orm/releases/tag/4.11.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`extendedWhereUnique`](/orm/v7/reference/prisma-client-reference#filter-on-non-unique-fields-with-userwhereuniqueinput) | [4.5.0](https://github.com/prisma/orm/releases/tag/4.5.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`fieldReference`](/orm/v7/reference/prisma-client-reference#compare-columns-in-the-same-table) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [5.0.0](https://github.com/prisma/orm/releases/tag/5.0.0) | +| [`clientExtensions`](/orm/v7/prisma-client/client-extensions) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`filteredRelationCount`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#filter-the-relation-count) | [4.3.0](https://github.com/prisma/orm/releases/tag/4.3.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`tracing`](/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing) | [4.2.0](https://github.com/prisma/orm/releases/tag/4.2.0) | [6.1.0](https://github.com/prisma/orm/releases/tag/6.1.0) | +| [`orderByNulls`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-with-null-records-first-or-last) | [4.1.0](https://github.com/prisma/orm/releases/tag/4.1.0) | [4.16.0](https://github.com/prisma/orm/releases/tag/4.16.0) | +| [`referentialIntegrity`](/orm/v7/prisma-schema/data-model/relations/relation-mode) | [3.1.1](https://github.com/prisma/orm/releases/tag/3.1.1) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0) | +| [`interactiveTransactions`](/orm/v7/prisma-client/queries/transactions#interactive-transactions) | [2.29.0](https://github.com/prisma/orm/releases/tag/2.29.0) | [4.7.0](https://github.com/prisma/orm/releases/tag/4.7.0)
with Prisma Accelerate [5.1.1](https://github.com/prisma/orm/releases/tag/5.1.1) | +| [`extendedIndexes`](/orm/v7/prisma-schema/data-model/indexes) | [3.5.0](https://github.com/prisma/orm/releases/tag/3.5.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`filterJson`](/orm/v7/prisma-client/special-fields-and-types/working-with-json-fields#filter-on-a-json-field-simple) | [2.23.0](https://github.com/prisma/orm/releases/tag/2.23.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`improvedQueryRaw`](/orm/v7/prisma-client/using-raw-sql/raw-queries#raw-query-type-mapping) | [3.14.0](https://github.com/prisma/orm/releases/tag/3.14.0) | [4.0.0](https://github.com/prisma/orm/releases/tag/4.0.0) | +| [`cockroachdb`](/orm/v7/core-concepts/supported-databases/postgresql#cockroachdb) | [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0)
migrations in [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) | [3.14.0](https://github.com/prisma/orm/releases/tag/3.14.0) | +| [`mongodb`](/orm/v7/core-concepts/supported-databases/mongodb) | [2.27.0](https://github.com/prisma/orm/releases/tag/2.27.0)
introspection in [3.2.0](https://github.com/prisma/orm/releases/tag/3.2.0)
embedded docs in [3.4.0](https://github.com/prisma/orm/releases/tag/3.4.0)
raw queries in [3.9.0](https://github.com/prisma/orm/releases/tag/3.9.0)
filters/ordering in embedded docs in [3.11.0](https://github.com/prisma/orm/releases/tag/3.11.0) | [3.12.0](https://github.com/prisma/orm/releases/tag/3.12.0) | +| [`microsoftSqlServer`](/orm/v7/core-concepts/supported-databases/sql-server) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`namedConstraints`](/orm/v7/prisma-schema/data-model/database-mapping#constraint-and-index-names) | [2.29.0](https://github.com/prisma/orm/releases/tag/2.29.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`referentialActions`](/orm/v7/prisma-schema/data-model/relations/referential-actions) | [2.26.0](https://github.com/prisma/orm/releases/tag/2.26.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`orderByAggregateGroup`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#order-by-aggregate-group) | [2.21.0](https://github.com/prisma/orm/releases/tag/2.21.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`orderByRelation`](/orm/v6/prisma-client/queries/filtering-and-sorting#sort-by-relation) | [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0)
aggregates in [2.19.0](https://github.com/prisma/orm/releases/tag/2.19.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`selectRelationCount`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#count-relations) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| `napi` | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | [3.0.1](https://github.com/prisma/orm/releases/tag/3.0.1) | +| [`groupBy`](/orm/v7/reference/prisma-client-reference#groupby) | [2.14.0](https://github.com/prisma/orm/releases/tag/2.14.0) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | +| [`createMany`](/orm/v7/reference/prisma-client-reference#createmany) | [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0) | [2.20.0](https://github.com/prisma/orm/releases/tag/2.20.0) | +| [`nativeTypes`](/orm/v7/prisma-schema/data-model/models#native-types-mapping) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) | +| [`uncheckedScalarInputs`](/orm/v7/prisma-client/queries/relation-queries#create-a-single-record-and-multiple-related-records) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | [2.15.0](https://github.com/prisma/orm/releases/tag/2.15.0) | +| [`transactionApi`](/orm/v7/prisma-client/queries/transactions#the-transaction-api) | [2.1.0](https://github.com/prisma/orm/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | +| [`connectOrCreate`](/orm/v7/reference/prisma-client-reference#connectorcreate) | [2.1.0](https://github.com/prisma/orm/releases/tag/2.1.0) | [2.11.0](https://github.com/prisma/orm/releases/tag/2.11.0) | +| [`atomicNumberOperations`](/orm/v7/reference/prisma-client-reference#atomic-number-operations) | [2.6.0](https://github.com/prisma/orm/releases/tag/2.6.0) | [2.10.0](https://github.com/prisma/orm/releases/tag/2.10.0) | +| [`insensitiveFilters` (PostgreSQL)](/orm/v6/prisma-client/queries/filtering-and-sorting#case-insensitive-filtering) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | [2.8.0](https://github.com/prisma/orm/releases/tag/2.8.0) | +| [`aggregateApi`](/orm/v7/prisma-client/queries/aggregation-grouping-summarizing#aggregate) | [2.2.0](https://github.com/prisma/orm/releases/tag/2.2.0) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | +| [`distinct`](/orm/v7/reference/prisma-client-reference#distinct) | [2.3.0](https://github.com/prisma/orm/releases/tag/2.3.0) | [2.5.0](https://github.com/prisma/orm/releases/tag/2.5.0) | diff --git a/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx b/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx index e2205b28c9..421d87e582 100644 --- a/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx @@ -1514,7 +1514,7 @@ Other options: | Options | Required | Description | Notes | | :--------------- | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------ | :----------------------------------------------------------------------------- | | `--script` | No | Outputs a SQL script instead of the default human-readable summary | Not supported in MongoDB | -| `-o`, `--output` | No | Writes to a file instead of stdout | Available since [5.12.1](https://github.com/prisma/prisma/releases/tag/5.12.1) | +| `-o`, `--output` | No | Writes to a file instead of stdout | Available since [5.12.1](https://github.com/prisma/orm/releases/tag/5.12.1) | | `--exit-code` | No | Change the exit code behavior to signal if the diff is empty or not (Empty: 0, Error: 1, Not empty: 2). Default behavior is Success: 0, Error: 1. | | | `--config` | No | Custom path to your Prisma config file | | | `--help` | No | Displays the help message | | diff --git a/apps/docs/content/docs/orm/v7/reference/prisma-client-reference.mdx b/apps/docs/content/docs/orm/v7/reference/prisma-client-reference.mdx index 5c1082dce4..74be67b2bd 100644 --- a/apps/docs/content/docs/orm/v7/reference/prisma-client-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/prisma-client-reference.mdx @@ -2729,7 +2729,7 @@ const user = await prisma.profile.create({ }); ``` -However, you can't use both the direct approach and the `connect` approach in the same query. See [this issue comment](https://github.com/prisma/prisma/issues/4322#issuecomment-737976117) for details. +However, you can't use both the direct approach and the `connect` approach in the same query. See [this issue comment](https://github.com/prisma/orm/issues/4322#issuecomment-737976117) for details. ##### Create a new `Post` record and connect it to an existing `User` record diff --git a/apps/docs/content/docs/orm/v7/reference/prisma-config-reference.mdx b/apps/docs/content/docs/orm/v7/reference/prisma-config-reference.mdx index 02f38a71c8..4694e45174 100644 --- a/apps/docs/content/docs/orm/v7/reference/prisma-config-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/prisma-config-reference.mdx @@ -366,7 +366,7 @@ export default { :::note -As of [Prisma ORM v6.11.0](https://github.com/prisma/prisma/releases/tag/6.11.0), the D1 adapter has been renamed from `PrismaD1HTTP` to `PrismaD1`. +As of [Prisma ORM v6.11.0](https://github.com/prisma/orm/releases/tag/6.11.0), the D1 adapter has been renamed from `PrismaD1HTTP` to `PrismaD1`. ::: diff --git a/apps/docs/content/docs/orm/v7/reference/prisma-schema-reference.mdx b/apps/docs/content/docs/orm/v7/reference/prisma-schema-reference.mdx index a57dcccf7e..a7803e5c6c 100644 --- a/apps/docs/content/docs/orm/v7/reference/prisma-schema-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/prisma-schema-reference.mdx @@ -351,7 +351,7 @@ Defines a Prisma [model](/orm/v7/prisma-schema/data-model/models#defining-models - Model names must adhere to the following regular expression: `[A-Za-z][A-Za-z0-9_]*` - Model names must start with a letter and are typically spelled in [PascalCase](https://wiki.c2.com/?PascalCase) - Model names should use the singular form (for example, `User` instead of `user`, `users` or `Users`) -- Prisma ORM has a number of **reserved words** that are being used by Prisma ORM internally and therefore cannot be used as a model name. You can find the reserved words [here](https://github.com/prisma/prisma/blob/6.5.0/packages/client/src/generation/generateClient.ts#L556-L605) and [here](https://github.com/prisma/prisma-engines/blob/main/psl/parser-database/src/names/reserved_model_names.rs#L44). +- Prisma ORM has a number of **reserved words** that are being used by Prisma ORM internally and therefore cannot be used as a model name. You can find the reserved words [here](https://github.com/prisma/orm/blob/6.5.0/packages/client/src/generation/generateClient.ts#L556-L605) and [here](https://github.com/prisma/prisma-engines/blob/main/psl/parser-database/src/names/reserved_model_names.rs#L44). > **Note**: You can use the [`@@map` attribute](#map-1) to map a model (for example, `User`) to a table with a different name that does not match model naming conventions (for example, `users`). @@ -1007,7 +1007,7 @@ The [MongoDB connector](/orm/v7/core-concepts/supported-databases/mongodb) does ::: -The `Unsupported` type was introduced in [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and allows you to represent data types in the Prisma schema that are not supported by Prisma Client. Fields of type `Unsupported` can be created during Introspection with `prisma db pull` or written by hand, and created in the database with Prisma Migrate or `db push`. +The `Unsupported` type was introduced in [2.17.0](https://github.com/prisma/orm/releases/tag/2.17.0) and allows you to represent data types in the Prisma schema that are not supported by Prisma Client. Fields of type `Unsupported` can be created during Introspection with `prisma db pull` or written by hand, and created in the database with Prisma Migrate or `db push`. #### Remarks @@ -2481,7 +2481,7 @@ Automatically stores the time when a record was last updated. If you do not supp :::warning -In versions before [4.4.0](https://github.com/prisma/prisma/releases/tag/4.4.0), if you're also using [`now()`](/orm/v7/reference/prisma-schema-reference#now), the time might differ from the `@updatedAt` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. +In versions before [4.4.0](https://github.com/prisma/orm/releases/tag/4.4.0), if you're also using [`now()`](/orm/v7/reference/prisma-schema-reference#now), the time might differ from the `@updatedAt` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. ::: @@ -2985,7 +2985,7 @@ Set a timestamp of the time when a record is created. :::warning -In versions before [4.4.0](https://github.com/prisma/prisma/releases/tag/4.4.0), if you're also using [`@updatedAt`](/orm/v7/reference/prisma-schema-reference#updatedat), the time might differ from the `now()` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. +In versions before [4.4.0](https://github.com/prisma/orm/releases/tag/4.4.0), if you're also using [`@updatedAt`](/orm/v7/reference/prisma-schema-reference#updatedat), the time might differ from the `now()` values if your database and app have different time zones. This happens because `@updatedAt` operates at the Prisma ORM level, while `now()` operates at the database level. ::: diff --git a/apps/docs/content/docs/orm/v7/reference/supported-databases.mdx b/apps/docs/content/docs/orm/v7/reference/supported-databases.mdx index 02b5764dd4..5117252415 100644 --- a/apps/docs/content/docs/orm/v7/reference/supported-databases.mdx +++ b/apps/docs/content/docs/orm/v7/reference/supported-databases.mdx @@ -55,4 +55,4 @@ Note that a fixed version of SQLite is shipped with every Prisma ORM release. | Cloudflare D1 (Preview) | \* | | Aiven (MySQL & Postgres) | \* | -¹ This does not include support for [Data API for Aurora Serverless](https://github.com/prisma/prisma/issues/1964). +¹ This does not include support for [Data API for Aurora Serverless](https://github.com/prisma/orm/issues/1964). diff --git a/apps/docs/vercel.json b/apps/docs/vercel.json index 0c45f88de1..009ddb1fe2 100644 --- a/apps/docs/vercel.json +++ b/apps/docs/vercel.json @@ -2197,27 +2197,27 @@ }, { "source": "/docs/guides/general-guides/database-workflows/sql-views", - "destination": "https://github.com/prisma/prisma/issues/678", + "destination": "https://github.com/prisma/orm/issues/678", "permanent": true }, { "source": "/docs/guides/general-guides/database-workflows/sql-views-postgres", - "destination": "https://github.com/prisma/prisma/issues/678", + "destination": "https://github.com/prisma/orm/issues/678", "permanent": true }, { "source": "/docs/guides/database/advanced-database-tasks/sql-views-postgres", - "destination": "https://github.com/prisma/prisma/issues/678", + "destination": "https://github.com/prisma/orm/issues/678", "permanent": true }, { "source": "/docs/guides/general-guides/database-workflows/sql-views-mysql", - "destination": "https://github.com/prisma/prisma/issues/678", + "destination": "https://github.com/prisma/orm/issues/678", "permanent": true }, { "source": "/docs/guides/database/advanced-database-tasks/sql-views-mysql", - "destination": "https://github.com/prisma/prisma/issues/678", + "destination": "https://github.com/prisma/orm/issues/678", "permanent": true }, { @@ -3852,7 +3852,7 @@ }, { "source": "/docs/guides/other/troubleshooting-orm/creating-bug-reports", - "destination": "https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&projects=&template=bug_report.yml", + "destination": "https://github.com/prisma/orm/issues/new?assignees=&labels=kind/bug&projects=&template=bug_report.yml", "permanent": true }, { @@ -4102,7 +4102,7 @@ }, { "source": "/docs/orm/more/help-and-troubleshooting/creating-bug-reports", - "destination": "https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&projects=&template=bug_report.yml", + "destination": "https://github.com/prisma/orm/issues/new?assignees=&labels=kind/bug&projects=&template=bug_report.yml", "permanent": true }, { diff --git a/apps/site/content/changelog/2024-03-13.mdx b/apps/site/content/changelog/2024-03-13.mdx index f2d1a9eb59..b769900247 100644 --- a/apps/site/content/changelog/2024-03-13.mdx +++ b/apps/site/content/changelog/2024-03-13.mdx @@ -53,7 +53,7 @@ With Prisma ORM, you can create multiple new records in nested queries, for ex In previous versions, Prisma ORM would translate this into multiple SQL `INSERT` queries, each requiring its own roundtrip to the database. As of this release, these nested `create` queries are optimized and the `INSERT` queries are sent to the database *in bulk* in a single roundtrip. -**👉 Read more** in our [5.11.0 release notes](https://github.com/prisma/prisma/releases/tag/5.11.0). +**👉 Read more** in our [5.11.0 release notes](https://github.com/prisma/orm/releases/tag/5.11.0). ## Join the Prisma Partner Network diff --git a/apps/site/content/changelog/2024-04-03.mdx b/apps/site/content/changelog/2024-04-03.mdx index 0462612bf2..c75f6054a1 100644 --- a/apps/site/content/changelog/2024-04-03.mdx +++ b/apps/site/content/changelog/2024-04-03.mdx @@ -24,11 +24,11 @@ Read more in our latest [blog post](https://www.prisma.io/blog/build-application ## Implementing `createMany()` for SQLite -Bringing support for `createMany()` in SQLite has been a [long-awaited and highly requested feature](https://github.com/prisma/prisma/issues/10710) ⭐ +Bringing support for `createMany()` in SQLite has been a [long-awaited and highly requested feature](https://github.com/prisma/orm/issues/10710) ⭐ -`createMany()` is a method on Prisma Client, released back in version [2.16.0](https://github.com/prisma/prisma/releases/tag/2.16.0), that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data. +`createMany()` is a method on Prisma Client, released back in version [2.16.0](https://github.com/prisma/orm/releases/tag/2.16.0), that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data. -Read more in our latest [release notes](https://github.com/prisma/prisma/releases/tag/5.12.0). +Read more in our latest [release notes](https://github.com/prisma/orm/releases/tag/5.12.0). ## Platform Console Updates diff --git a/apps/site/content/changelog/2024-04-25.mdx b/apps/site/content/changelog/2024-04-25.mdx index 9e0a3e1514..e25ee6cf3e 100644 --- a/apps/site/content/changelog/2024-04-25.mdx +++ b/apps/site/content/changelog/2024-04-25.mdx @@ -21,15 +21,15 @@ Learn more in our [blog post](https://www.prisma.io/blog/accelerate-static-ip-su ## `omit` Fields From Prisma Client Queries (In Preview) -We’re excited to announce Preview support for the `omit` option within the Prisma Client query options. The [highly-requested](https://github.com/prisma/prisma/issues/5042) `omit` feature now allows you to exclude fields that you don’t want to retrieve from the database on a **per-query basis**. +We’re excited to announce Preview support for the `omit` option within the Prisma Client query options. The [highly-requested](https://github.com/prisma/orm/issues/5042) `omit` feature now allows you to exclude fields that you don’t want to retrieve from the database on a **per-query basis**. Here is an example of using `omit`: ![omit-code-example.png](/changelog/image-d524983761b9b4504198b546eaea9162ea0b4b97-1040x540-png-omit-code-example.png) -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](https://github.com/prisma/prisma/issues/5042). +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](https://github.com/prisma/orm/issues/5042). -Read more in our latest [release notes](https://github.com/prisma/prisma/releases/tag/5.13.0) +Read more in our latest [release notes](https://github.com/prisma/orm/releases/tag/5.13.0) ## Doc Updates diff --git a/apps/site/content/changelog/2024-05-15.mdx b/apps/site/content/changelog/2024-05-15.mdx index d106183725..0a4c99c010 100644 --- a/apps/site/content/changelog/2024-05-15.mdx +++ b/apps/site/content/changelog/2024-05-15.mdx @@ -29,7 +29,7 @@ Here’s an example of creating multiple posts and then immediately returning th ![Code export (1).png](/changelog/image-5fc540292aa61c9d17742aa50eee4a6bf9aef81d-1040x522-png-Code-export-1-.png) -Read more in our [release notes](https://github.com/prisma/prisma/releases/tag/5.14.0) +Read more in our [release notes](https://github.com/prisma/orm/releases/tag/5.14.0) ## MongoDB performance improvements @@ -37,7 +37,7 @@ Previously, Prisma ORM suffered from performance issues when using the `in` op 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. -See the closed public issues in our [release notes](https://github.com/prisma/prisma/releases/tag/5.14.0). +See the closed public issues in our [release notes](https://github.com/prisma/orm/releases/tag/5.14.0). ## Prisma ORM Benchmark diff --git a/apps/site/content/changelog/2024-06-06.mdx b/apps/site/content/changelog/2024-06-06.mdx index 22be70e110..aa22c8a39d 100644 --- a/apps/site/content/changelog/2024-06-06.mdx +++ b/apps/site/content/changelog/2024-06-06.mdx @@ -22,7 +22,7 @@ Interested in learning more and trying Pulse for yourself? [Dive into our blog p ## Organize your Prisma Schema into Multiple Files in v5.15 -We are excited to introduce a new Preview feature in Prisma ORM: the ability to organize your Prisma Schema into multiple files. This highly requested feature is now available in our [5.15.0 release](https://github.com/prisma/prisma/releases/tag/5.15.0)! +We are excited to introduce a new Preview feature in Prisma ORM: the ability to organize your Prisma Schema into multiple files. This highly requested feature is now available in our [5.15.0 release](https://github.com/prisma/orm/releases/tag/5.15.0)! ![blogpost-splitschema 4.png](/changelog/image-4447786d03b362ef21329948b4c9d48d90ddbe9f-1200x630-png-blogpost-splitschema-4.png) diff --git a/apps/site/content/changelog/2024-06-27.mdx b/apps/site/content/changelog/2024-06-27.mdx index b2e072acb9..0dfdbfcb54 100644 --- a/apps/site/content/changelog/2024-06-27.mdx +++ b/apps/site/content/changelog/2024-06-27.mdx @@ -13,7 +13,7 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -In [5.13.0](https://github.com/prisma/prisma/releases/tag/5.13.0), we introduced Preview support for the `omit` option within the Prisma Client query options. Now, we’re more than happy to announce that we’re expanding the `omitApi` Preview feature to also include the ability to **omit fields globally**. +In [5.13.0](https://github.com/prisma/orm/releases/tag/5.13.0), we introduced Preview support for the `omit` option within the Prisma Client query options. Now, we’re more than happy to announce that we’re expanding the `omitApi` Preview feature to also include the ability to **omit fields globally**. Here's an example how you’re able to define fields to omit when instantiating Prisma Client either locally or globally: diff --git a/apps/site/content/changelog/2024-07-18.mdx b/apps/site/content/changelog/2024-07-18.mdx index f99defec55..31d6222df1 100644 --- a/apps/site/content/changelog/2024-07-18.mdx +++ b/apps/site/content/changelog/2024-07-18.mdx @@ -17,7 +17,7 @@ We’ve changed the response format of `queryRaw` to decrease its average size ![perf-graphs.png](/changelog/image-a6312279b8aab81d7fcf21ad3308dd3a18710c7f-2724x1566-png-perf-graphs.png) -When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements, as you can clearly see in the graphs. We are very excited to introduce these improvements in our latest [5.17.0 release](https://github.com/prisma/prisma/releases/tag/5.17.0)! +When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements, as you can clearly see in the graphs. We are very excited to introduce these improvements in our latest [5.17.0 release](https://github.com/prisma/orm/releases/tag/5.17.0)! ## **VSCode extension improvements** @@ -29,7 +29,7 @@ Some of the additions were: - Added context on hover - Additional quick fixes -Find out more in our latest [release notes](https://github.com/prisma/prisma/releases/tag/5.17.0). +Find out more in our latest [release notes](https://github.com/prisma/orm/releases/tag/5.17.0). ## Going beyond Prisma ORM diff --git a/apps/site/content/changelog/2024-08-08.mdx b/apps/site/content/changelog/2024-08-08.mdx index 69e8644ed6..1b80bf4849 100644 --- a/apps/site/content/changelog/2024-08-08.mdx +++ b/apps/site/content/changelog/2024-08-08.mdx @@ -18,7 +18,7 @@ source: To support this, we’ve updated the `uuid()` function in Prisma Schema to accept an optional integer argument. Right now, the only valid values are `4` and `7`, with `4` being the default. -More details in our [latest release notes](https://github.com/prisma/prisma/releases/tag/5.18.0). +More details in our [latest release notes](https://github.com/prisma/orm/releases/tag/5.18.0). ![Code export (4).png](/changelog/image-0e65ac228e56ab655cadd7cefc48e651489de118-2876x1672-png-Code-export-4-.png) diff --git a/apps/site/content/changelog/2024-09-26.mdx b/apps/site/content/changelog/2024-09-26.mdx index d50b25bc5c..69e8383e32 100644 --- a/apps/site/content/changelog/2024-09-26.mdx +++ b/apps/site/content/changelog/2024-09-26.mdx @@ -36,11 +36,11 @@ This highly requested feature allows you to configure query limits based on your ## Introducing `strictUndefinedChecks` feature in Preview! -With Prisma ORM 5.20.0, the Preview feature `strictUndefinedChecks` will disallow any value that is explicitly `undefined` and will be a runtime error. This change is direct feedback from [this GitHub issue](https://github.com/prisma/prisma/issues/20169) and follows [our latest proposal](https://github.com/prisma/prisma/issues/20169#issuecomment-2338360300) on the same issue. +With Prisma ORM 5.20.0, the Preview feature `strictUndefinedChecks` will disallow any value that is explicitly `undefined` and will be a runtime error. This change is direct feedback from [this GitHub issue](https://github.com/prisma/orm/issues/20169) and follows [our latest proposal](https://github.com/prisma/orm/issues/20169#issuecomment-2338360300) on the same issue. ![Code export (6).png](/changelog/image-02452d28050185410c782423320d0f1319ab49e1-2804x952-png-Code-export-6-.png) -If you want to read and learn more, take a look at our latest [release notes](https://github.com/prisma/prisma/releases/tag/5.20.0)! +If you want to read and learn more, take a look at our latest [release notes](https://github.com/prisma/orm/releases/tag/5.20.0)! ## Build real-time workflows with Pulse & Inngest diff --git a/apps/site/content/changelog/2024-10-17.mdx b/apps/site/content/changelog/2024-10-17.mdx index d11db55285..8249527fef 100644 --- a/apps/site/content/changelog/2024-10-17.mdx +++ b/apps/site/content/changelog/2024-10-17.mdx @@ -37,7 +37,7 @@ Check out the new landing page: [https://www.prisma.io/blog](https://www.prisma. Prisma ORM 5.21.0 brings some bug fixes and needed enhancements so that we can move our `tracing` Preview feature to GA. -[More info in our release notes!](https://github.com/prisma/prisma/releases/tag/5.21.0) +[More info in our release notes!](https://github.com/prisma/orm/releases/tag/5.21.0) ## Hiring diff --git a/apps/site/content/changelog/2024-11-07.mdx b/apps/site/content/changelog/2024-11-07.mdx index aa63646aac..f286a9413d 100644 --- a/apps/site/content/changelog/2024-11-07.mdx +++ b/apps/site/content/changelog/2024-11-07.mdx @@ -21,9 +21,9 @@ We’re confident that the technology powering Prisma Postgres is the path forwa ## 📈 Prisma ORM 5.22.0 -We’re continuing to improve the Prisma ORM experience with [Prisma ORM 5.22.0](https://github.com/prisma/prisma/releases/tag/5.22.0). In this release we focused on improving the `tracing` Preview feature and fix annoying bugs in metrics and connection pooling. +We’re continuing to improve the Prisma ORM experience with [Prisma ORM 5.22.0](https://github.com/prisma/orm/releases/tag/5.22.0). In this release we focused on improving the `tracing` Preview feature and fix annoying bugs in metrics and connection pooling. -[More info available in our release notes!](https://github.com/prisma/prisma/releases/tag/5.22.0) +[More info available in our release notes!](https://github.com/prisma/orm/releases/tag/5.22.0) ## 👀 Prisma in the wild diff --git a/apps/site/content/changelog/2024-11-28.mdx b/apps/site/content/changelog/2024-11-28.mdx index f48667f9bc..6e6f8111a9 100644 --- a/apps/site/content/changelog/2024-11-28.mdx +++ b/apps/site/content/changelog/2024-11-28.mdx @@ -17,7 +17,7 @@ Prisma 6 is here, bringing improvements for future-proofing and enhanced perform - **Explore what's new**: Read the [launch blog](https://pris.ly/prisma-6?utm_source=website&utm_medium=changelog) to learn how Prisma has evolved, including tooling updates and new features for improved performance and flexibility. - **Upgrade guide**: Check the [migration guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6?utm_source=website&utm_medium=changelog) for instructions to upgrade your Prisma setup. -- **Detailed release notes**: Dive into the [release notes](https://github.com/prisma/prisma/releases/tag/6.0.0) for a comprehensive look at individual feature updates. +- **Detailed release notes**: Dive into the [release notes](https://github.com/prisma/orm/releases/tag/6.0.0) for a comprehensive look at individual feature updates. ## 💚 Prisma Postgres is free in early access diff --git a/apps/site/content/changelog/2024-12-19.mdx b/apps/site/content/changelog/2024-12-19.mdx index ac2e801ad4..6c8b72f777 100644 --- a/apps/site/content/changelog/2024-12-19.mdx +++ b/apps/site/content/changelog/2024-12-19.mdx @@ -11,7 +11,7 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -We’re really excited about Prisma ORM 6.1.0 as our `tracing` Preview feature is now stable! There are a few changes needed if you are using the `tracing` feature, make sure you check out [the release notes](https://github.com/prisma/prisma/releases/tag/6.1.0) for all the details. +We’re really excited about Prisma ORM 6.1.0 as our `tracing` Preview feature is now stable! There are a few changes needed if you are using the `tracing` feature, make sure you check out [the release notes](https://github.com/prisma/orm/releases/tag/6.1.0) for all the details. ## 📜 Our Manifesto for Prisma ORM @@ -47,4 +47,4 @@ The Prisma team has been hard at work writing as well as building. ## 🤝 Thanks -As we wrap up this installment of the Changelog (and 2024!), the Prisma team wants to thank our community. In addition to the [ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) where we re-commit ourselves to the community, we also are celebrating [40,000 stars on our GitHub repo](https://github.com/prisma/prisma). We’ve come a long way, but this is only the beginning for Prisma and we couldn’t be happier having you along with us. +As we wrap up this installment of the Changelog (and 2024!), the Prisma team wants to thank our community. In addition to the [ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) where we re-commit ourselves to the community, we also are celebrating [40,000 stars on our GitHub repo](https://github.com/prisma/orm). We’ve come a long way, but this is only the beginning for Prisma and we couldn’t be happier having you along with us. diff --git a/apps/site/content/changelog/2025-01-09.mdx b/apps/site/content/changelog/2025-01-09.mdx index 6c35e12b59..64258696ba 100644 --- a/apps/site/content/changelog/2025-01-09.mdx +++ b/apps/site/content/changelog/2025-01-09.mdx @@ -11,7 +11,7 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -Prisma ORM 6.2.0 might be a minor release, but the changes in it are **major.** In this release we are moving the omit API ([our most requested feature](https://github.com/prisma/prisma/issues/5042)) to Generally Available. You can now use the omit API without a Preview feature flag! +Prisma ORM 6.2.0 might be a minor release, but the changes in it are **major.** In this release we are moving the omit API ([our most requested feature](https://github.com/prisma/orm/issues/5042)) to Generally Available. You can now use the omit API without a Preview feature flag! 6.2.0 also includes some other highly requested features: @@ -19,7 +19,7 @@ Prisma ORM 6.2.0 might be a minor release, but the changes in it are **major.** - `updateManyAndReturn` support - Support for auto-generated ULID values -As always, [check out the release notes](https://github.com/prisma/prisma/releases/tag/6.2.0) for all the details. +As always, [check out the release notes](https://github.com/prisma/orm/releases/tag/6.2.0) for all the details. ## 🤖 Ask AI makes its way to the Console diff --git a/apps/site/content/changelog/2025-01-30.mdx b/apps/site/content/changelog/2025-01-30.mdx index 9e86a30245..a01564a9cc 100644 --- a/apps/site/content/changelog/2025-01-30.mdx +++ b/apps/site/content/changelog/2025-01-30.mdx @@ -30,11 +30,11 @@ Alongside Prisma Studio updates, Prisma ORM 6.3.0 comes with some quality of lif - `generator` fields are now sorted deterministically (no more random changes!) - Replaced `NOT IN` with `NOT EXISTS` in relation filters -As always, [check out the release notes](https://github.com/prisma/prisma/releases/tag/6.3.0) for all the details. +As always, [check out the release notes](https://github.com/prisma/orm/releases/tag/6.3.0) for all the details. ## 🫣 Preview features no longer uncertain -In [our ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) we noted that we had several Preview features that have gone stale with no updates in several years. We’re happy to report that our ORM team has gone through the existing features and their implementations and [provided a plan on our GitHub](https://github.com/prisma/prisma/discussions/26136) on how they will be tackled! +In [our ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) we noted that we had several Preview features that have gone stale with no updates in several years. We’re happy to report that our ORM team has gone through the existing features and their implementations and [provided a plan on our GitHub](https://github.com/prisma/orm/discussions/26136) on how they will be tackled! As a reminder, once a feature enters Preview, we plan to retire or promote that feature within the next three month period. diff --git a/apps/site/content/changelog/2025-03-13.mdx b/apps/site/content/changelog/2025-03-13.mdx index abd965ae92..1a907f327b 100644 --- a/apps/site/content/changelog/2025-03-13.mdx +++ b/apps/site/content/changelog/2025-03-13.mdx @@ -19,7 +19,7 @@ source: Our ORM team is making progress on our transition from Rust to TypeScript. We've developed [a migration plan](https://www.prisma.io/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm) and now have [an initial prototype with benchmarks](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance)! -This quarter we will be keeping our momentum by releasing support for different databases one by one. You can read up on that in [our latest ORM Roadmap](https://github.com/prisma/prisma/issues/26592). +This quarter we will be keeping our momentum by releasing support for different databases one by one. You can read up on that in [our latest ORM Roadmap](https://github.com/prisma/orm/issues/26592). ## 🔒 Prisma ORM 6.5.0 diff --git a/apps/site/content/changelog/2025-04-10.mdx b/apps/site/content/changelog/2025-04-10.mdx index 510f9367e1..158ecd6522 100644 --- a/apps/site/content/changelog/2025-04-10.mdx +++ b/apps/site/content/changelog/2025-04-10.mdx @@ -17,7 +17,7 @@ source: --- [Prisma Postgres](https://www.prisma.io/postgres) is the first serverless database without cold starts. Designed for optimal efficiency and high performance, it's the perfect database to be used alongside AI tools like Cursor, Windsurf, Lovable or co.dev. -In the [v6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0) ORM release, we added a command to start a Prisma MCP server that you can integrate in your AI development environment. Thanks to that MCP server, you can now: +In the [v6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0) ORM release, we added a command to start a Prisma MCP server that you can integrate in your AI development environment. Thanks to that MCP server, you can now: - tell your AI agent to create new DB instances - design your data model @@ -42,7 +42,7 @@ Read more about the MCP server on our blog: [**Announcing Prisma's MCP Server: V ## 🚀 Prisma ORM 6.6.0 -Prisma ORM [v6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0) comes packed with amazing features: +Prisma ORM [v6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0) comes packed with amazing features: #### **A modern and flexible `prisma-client` generator with ESM support (Early Access)** diff --git a/apps/site/content/changelog/2025-05-01.mdx b/apps/site/content/changelog/2025-05-01.mdx index 0bbaf58980..da1355a5ad 100644 --- a/apps/site/content/changelog/2025-05-01.mdx +++ b/apps/site/content/changelog/2025-05-01.mdx @@ -74,9 +74,9 @@ The `prismaSchemaFolder` Preview feature is moving into General Availability #### **Splitting generated output with new `prisma-client` generator (Preview)** -With the `prisma-client-js` generator, the generated Prisma Client library is put into a single `index.d.ts` file. This sometimes led to [issues](https://github.com/prisma/prisma/issues/4807) with large schemas where the size of the generated output could slow down code editors and break auto-complete. +With the `prisma-client-js` generator, the generated Prisma Client library is put into a single `index.d.ts` file. This sometimes led to [issues](https://github.com/prisma/orm/issues/4807) with large schemas where the size of the generated output could slow down code editors and break auto-complete. -As of this release, our new `prisma-client` generator (that was released in [6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0)) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file. +As of this release, our new `prisma-client` generator (that was released in [6.6.0](https://github.com/prisma/orm/releases/tag/6.6.0)) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file. 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/v7/prisma-schema/overview/generators#output-splitting-and-importing-types). diff --git a/apps/site/content/changelog/2025-09-10.mdx b/apps/site/content/changelog/2025-09-10.mdx index 477d4f2814..d109b0ec52 100644 --- a/apps/site/content/changelog/2025-09-10.mdx +++ b/apps/site/content/changelog/2025-09-10.mdx @@ -93,7 +93,7 @@ generator client { } ``` -We’d love for you to try this out and share your feedback as we prepare for General Availability. Please [open an issue on GitHub](https://github.com/prisma/prisma/issues) if you encounter any problems or have suggestions. +We’d love for you to try this out and share your feedback as we prepare for General Availability. Please [open an issue on GitHub](https://github.com/prisma/orm/issues) if you encounter any problems or have suggestions. ## **🤝 Enterprise support** diff --git a/apps/site/content/changelog/2025-10-08.mdx b/apps/site/content/changelog/2025-10-08.mdx index 03e1b78ed9..4fc0f6b079 100644 --- a/apps/site/content/changelog/2025-10-08.mdx +++ b/apps/site/content/changelog/2025-10-08.mdx @@ -40,7 +40,7 @@ Here’s what’s new: Prisma ORM [v6.17.0](https://pris.ly/6.17.0) comes with a lot of bug fixes and improvements: -- Added support for Entra ID (ActiveDirectory) authentication parameters for the MS SQL Server driver adapter. For example, you can use the `config` object to configure [DefaultAzureCredential](https://learn.microsoft.com/en-gb/azure/developer/javascript/sdk/authentication/credential-chains#use-defaultazurecredential-for-flexibility): Learn more in this [PR](https://github.com/prisma/prisma/pull/28156/files#diff-351f5d894309f058776099c378e3956271f34f34c04e2b54576045b9773ab61aR61-R62). +- Added support for Entra ID (ActiveDirectory) authentication parameters for the MS SQL Server driver adapter. For example, you can use the `config` object to configure [DefaultAzureCredential](https://learn.microsoft.com/en-gb/azure/developer/javascript/sdk/authentication/credential-chains#use-defaultazurecredential-for-flexibility): Learn more in this [PR](https://github.com/prisma/orm/pull/28156/files#diff-351f5d894309f058776099c378e3956271f34f34c04e2b54576045b9773ab61aR61-R62). ```typescript import { PrismaMssql } from '@prisma/adapter-mssql' @@ -63,9 +63,9 @@ const prisma = new PrismaClient({ adapter }) ``` -- Relaxed the support package range for `@opentelemetry/instrumentation` to be compatible with `">=0.52.0 <1"`. Learn more in this [PR](https://github.com/prisma/prisma/pull/28199/files). -- Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this [PR](https://github.com/prisma/prisma/pull/28159). -- Fixed JSON column handling when using a MariaDB database. Learn more in this [PR](https://github.com/prisma/prisma/pull/28211). +- Relaxed the support package range for `@opentelemetry/instrumentation` to be compatible with `">=0.52.0 <1"`. Learn more in this [PR](https://github.com/prisma/orm/pull/28199/files). +- Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this [PR](https://github.com/prisma/orm/pull/28159). +- Fixed JSON column handling when using a MariaDB database. Learn more in this [PR](https://github.com/prisma/orm/pull/28211). - Restored the original behaviour of group-by aggregations where they would refer to columns with explicit table names which fixes a regression that would result in ambiguous column errors. Learn more in this [PR](https://github.com/prisma/prisma-engines/pull/5629). We are working hard on the upcoming Prisma v7 release! If you’re curious, you can learn more and start preparing for the future of Prisma ORM [here](https://pris.ly/launch/6.17.0). diff --git a/apps/site/content/changelog/2025-10-22.mdx b/apps/site/content/changelog/2025-10-22.mdx index d900a13c4d..652a9512f8 100644 --- a/apps/site/content/changelog/2025-10-22.mdx +++ b/apps/site/content/changelog/2025-10-22.mdx @@ -34,10 +34,10 @@ export default defineConfig({ }); ``` -- [\#28291](https://github.com/prisma/prisma/pull/28291) Support multiple Prisma instances with different providers -- [\#28305](https://github.com/prisma/prisma/pull/28305) Add `env` helper function -- [\#28266](https://github.com/prisma/prisma/pull/28266) Add support for `js` or `classic` as engine types in `prisma.config` -- [\#28139](https://github.com/prisma/prisma/pull/28139) Map `Bytes` to `Uint8Array` depending on Typescript version +- [\#28291](https://github.com/prisma/orm/pull/28291) Support multiple Prisma instances with different providers +- [\#28305](https://github.com/prisma/orm/pull/28305) Add `env` helper function +- [\#28266](https://github.com/prisma/orm/pull/28266) Add support for `js` or `classic` as engine types in `prisma.config` +- [\#28139](https://github.com/prisma/orm/pull/28139) Map `Bytes` to `Uint8Array` depending on Typescript version ### Database Metric in Console diff --git a/apps/site/content/changelog/2025-11-05.mdx b/apps/site/content/changelog/2025-11-05.mdx index ecf61acbfc..556b02f84b 100644 --- a/apps/site/content/changelog/2025-11-05.mdx +++ b/apps/site/content/changelog/2025-11-05.mdx @@ -18,7 +18,7 @@ Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s releas - [\#5675](https://github.com/prisma/prisma-engines/pull/5675): When dropping a model from a schema, do not append the default schema to the migration. - [\#5656](https://github.com/prisma/prisma-engines/pull/5656): Aligning naming conventions for fields and relation fields -- [\#28341](https://github.com/prisma/prisma/pull/28341): Add biome ignore comments to generated client files. This was a community contribution from [@lonelyevil](https://github.com/lonelyevil), thank you! +- [\#28341](https://github.com/prisma/orm/pull/28341): Add biome ignore comments to generated client files. This was a community contribution from [@lonelyevil](https://github.com/lonelyevil), thank you! ## Prisma Postgres diff --git a/apps/site/content/changelog/2025-11-19.mdx b/apps/site/content/changelog/2025-11-19.mdx index e76e9349c7..aa9de48e9b 100644 --- a/apps/site/content/changelog/2025-11-19.mdx +++ b/apps/site/content/changelog/2025-11-19.mdx @@ -231,12 +231,12 @@ export const PaymentProvider: { **Miscellaneous** -- [\#28493](https://github.com/prisma/prisma/pull/28493): Stop shimming `WeakRef` in Cloudflare Workers. This will now avoid any unexpected memory leaks. -- [\#28297](https://github.com/prisma/prisma/pull/28297): Remove hardcoded URL validation. Users are now required to make sure they don’t include sensitive information in their config files. -- [\#28273](https://github.com/prisma/prisma/pull/28273): Removed Prisma v1 detection -- [\#28343](https://github.com/prisma/prisma/pull/28343): Remove undocumented `--url` flag from `prisma db pull` -- [\#28286](https://github.com/prisma/prisma/pull/28286): Remove deprecated `prisma introspect` command. -- [\#28480](https://github.com/prisma/prisma/pull/28480): Rename `/wasm` to `/edge` +- [\#28493](https://github.com/prisma/orm/pull/28493): Stop shimming `WeakRef` in Cloudflare Workers. This will now avoid any unexpected memory leaks. +- [\#28297](https://github.com/prisma/orm/pull/28297): Remove hardcoded URL validation. Users are now required to make sure they don’t include sensitive information in their config files. +- [\#28273](https://github.com/prisma/orm/pull/28273): Removed Prisma v1 detection +- [\#28343](https://github.com/prisma/orm/pull/28343): Remove undocumented `--url` flag from `prisma db pull` +- [\#28286](https://github.com/prisma/orm/pull/28286): Remove deprecated `prisma introspect` command. +- [\#28480](https://github.com/prisma/orm/pull/28480): Rename `/wasm` to `/edge` - This change only affects `prisma-client-js` - Before: - `/edge` → meant “for Prisma Accelerate” diff --git a/apps/site/content/changelog/2025-12-03.mdx b/apps/site/content/changelog/2025-12-03.mdx index 8b51de6812..21fc02e3ee 100644 --- a/apps/site/content/changelog/2025-12-03.mdx +++ b/apps/site/content/changelog/2025-12-03.mdx @@ -13,13 +13,13 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -- [\#28735](https://github.com/prisma/prisma/pull/28735): **pnpm monorepo issues with prisma client runtime utils** Resolves issues in pnpm monorepos where users would report TypeScript issues related to `@prisma/client-runtime-utils`. -- [\#28769](https://github.com/prisma/prisma/pull/28769): **implement sql commenter plugins for Prisma Client** This PR implements support for SQL commenter plugins to Prisma Client. The feature will allow users to add metadata to SQL queries as comments, following the [sqlcommenter format](https://google.github.io/sqlcommenter/). Here are two related PRs that were also merged: - - [\#28796](https://github.com/prisma/prisma/pull/28796): **implement query tags for SQL commenter plugin** - - [\#28802](https://github.com/prisma/prisma/pull/28802): **add `traceContext` SQL commenter plugin** -- [\#28737](https://github.com/prisma/prisma/pull/28737): **added error message when constructing client without configs** This commit adds an error message when trying to create a new PrismaClient instance without any arguments. Thanks to @xio84 for this community contribution! -- [\#28820](https://github.com/prisma/prisma/pull/28820): **mark `@opentelemetry/api` as external in instrumentation** Ensures `@opentelemetry/api` is treated as an external dependency rather than bundled. Since it is a peer dependency, this prevents applications from ending up with duplicate copies of the package. -- [\#28694](https://github.com/prisma/prisma/pull/28694): **allow `env()` helper to accept interface-based generics** Updates the `env()` helper’s type definition so it works with interfaces as well as type aliases. This removes the previous constraint requiring an index signature and resolves TS2344 errors when using interface-based env types. Runtime behavior is unchanged. Thanks to @SaubhagyaAnubhav for this community contribution! +- [\#28735](https://github.com/prisma/orm/pull/28735): **pnpm monorepo issues with prisma client runtime utils** Resolves issues in pnpm monorepos where users would report TypeScript issues related to `@prisma/client-runtime-utils`. +- [\#28769](https://github.com/prisma/orm/pull/28769): **implement sql commenter plugins for Prisma Client** This PR implements support for SQL commenter plugins to Prisma Client. The feature will allow users to add metadata to SQL queries as comments, following the [sqlcommenter format](https://google.github.io/sqlcommenter/). Here are two related PRs that were also merged: + - [\#28796](https://github.com/prisma/orm/pull/28796): **implement query tags for SQL commenter plugin** + - [\#28802](https://github.com/prisma/orm/pull/28802): **add `traceContext` SQL commenter plugin** +- [\#28737](https://github.com/prisma/orm/pull/28737): **added error message when constructing client without configs** This commit adds an error message when trying to create a new PrismaClient instance without any arguments. Thanks to @xio84 for this community contribution! +- [\#28820](https://github.com/prisma/orm/pull/28820): **mark `@opentelemetry/api` as external in instrumentation** Ensures `@opentelemetry/api` is treated as an external dependency rather than bundled. Since it is a peer dependency, this prevents applications from ending up with duplicate copies of the package. +- [\#28694](https://github.com/prisma/orm/pull/28694): **allow `env()` helper to accept interface-based generics** Updates the `env()` helper’s type definition so it works with interfaces as well as type aliases. This removes the previous constraint requiring an index signature and resolves TS2344 errors when using interface-based env types. Runtime behavior is unchanged. Thanks to @SaubhagyaAnubhav for this community contribution! ## Read Replicas extension @@ -176,7 +176,7 @@ app.use( Additional framework examples for **Express**, **Koa**, **Fastify**, and **NestJS** are available in the documentation. -For complete documentation, see [SQL Comments](https://www.prisma.io/docs/orm/v7/prisma-client/observability-and-logging/sql-comments). We'd love to hear your feedback on this feature! Please open an issue on [GitHub](https://github.com/prisma/prisma) or join the discussion in our [Discord community](https://pris.ly/discord). +For complete documentation, see [SQL Comments](https://www.prisma.io/docs/orm/v7/prisma-client/observability-and-logging/sql-comments). We'd love to hear your feedback on this feature! Please open an issue on [GitHub](https://github.com/prisma/orm) or join the discussion in our [Discord community](https://pris.ly/discord). ## Enterprise support diff --git a/apps/site/content/changelog/2025-12-17.mdx b/apps/site/content/changelog/2025-12-17.mdx index aa696c9acb..edbb19465d 100644 --- a/apps/site/content/changelog/2025-12-17.mdx +++ b/apps/site/content/changelog/2025-12-17.mdx @@ -13,25 +13,25 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -- [\#28830](https://github.com/prisma/prisma/pull/28830): feat: add `sqlcommenter-query-insights` plugin +- [\#28830](https://github.com/prisma/orm/pull/28830): feat: add `sqlcommenter-query-insights` plugin - Adds a new SQL commenter plugin to support query insights metadata. -- [\#28860](https://github.com/prisma/prisma/pull/28860): feat(migrate): add `-url` param for `db pull`, `db push`, `migrate dev` +- [\#28860](https://github.com/prisma/orm/pull/28860): feat(migrate): add `-url` param for `db pull`, `db push`, `migrate dev` - Adds a `-url` flag to key migrate commands to make connection configuration more flexible. -- [\#28895](https://github.com/prisma/prisma/pull/28895): feat(config): allow undefined URLs in e.g. `prisma generate` +- [\#28895](https://github.com/prisma/orm/pull/28895): feat(config): allow undefined URLs in e.g. `prisma generate` - Allows certain workflows (such as `prisma generate`) to proceed even when URLs are undefined. -- [\#28903](https://github.com/prisma/prisma/pull/28903): feat(cli): customize `prisma init` based on the JS runtime (Bun vs others) +- [\#28903](https://github.com/prisma/orm/pull/28903): feat(cli): customize `prisma init` based on the JS runtime (Bun vs others) - Makes `prisma init` tailor generated setup depending on whether the runtime is Bun or another JavaScript runtime. -- [\#28846](https://github.com/prisma/prisma/pull/28846): fix(client-engine-runtime): make `DataMapperError` a `UserFacingError` +- [\#28846](https://github.com/prisma/orm/pull/28846): fix(client-engine-runtime): make `DataMapperError` a `UserFacingError` - Ensures `DataMapperError` is surfaced as a user-facing error for clearer, more actionable error reporting. -- [\#28849](https://github.com/prisma/prisma/pull/28849): fix(adapter-\{pg,neon,ppg\}): handle 22P02 error in Postgres +- [\#28849](https://github.com/prisma/orm/pull/28849): fix(adapter-\{pg,neon,ppg\}): handle 22P02 error in Postgres - Improves Postgres adapter error handling for invalid-text-representation errors (`22P02`). -- [\#28913](https://github.com/prisma/prisma/pull/28913): fix: fix byte upserts by removing legacy byte array representation +- [\#28913](https://github.com/prisma/orm/pull/28913): fix: fix byte upserts by removing legacy byte array representation - Fixes byte upsert behavior by removing a legacy byte-array representation path. -- [\#28535](https://github.com/prisma/prisma/pull/28535): fix(client,internals,migrate,generator-helper): handle multibyte UTF-8 characters split across chunk boundaries in byline +- [\#28535](https://github.com/prisma/orm/pull/28535): fix(client,internals,migrate,generator-helper): handle multibyte UTF-8 characters split across chunk boundaries in byline - Prevents issues when multibyte UTF-8 characters are split across chunk boundaries during line processing. -- [\#28911](https://github.com/prisma/prisma/pull/28911): fix(cli): make `prisma version --json` emit JSON only to stdout +- [\#28911](https://github.com/prisma/orm/pull/28911): fix(cli): make `prisma version --json` emit JSON only to stdout - Ensures machine-readable JSON output is emitted cleanly to stdout without extra noise. -- [\#28914](https://github.com/prisma/prisma/pull/28914): refactor(cli): bump `@prisma/dev` and use `startPrismaDevServer` instead of the deprecated `unstable_startServer` +- [\#28914](https://github.com/prisma/orm/pull/28914): refactor(cli): bump `@prisma/dev` and use `startPrismaDevServer` instead of the deprecated `unstable_startServer` - Migrates CLI dev server startup to the newer `startPrismaDevServer` API and updates `@prisma/dev`. ## VS Code Extension diff --git a/apps/site/content/changelog/2026-01-21.mdx b/apps/site/content/changelog/2026-01-21.mdx index 09ee7393f0..0784206442 100644 --- a/apps/site/content/changelog/2026-01-21.mdx +++ b/apps/site/content/changelog/2026-01-21.mdx @@ -13,7 +13,7 @@ share: source: exportedAt: "2026-03-31T10:29:19.701Z" --- -- [\#28976](https://github.com/prisma/prisma/pull/28976): Fast and Small Query Compilers +- [\#28976](https://github.com/prisma/orm/pull/28976): Fast and Small Query Compilers We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new `compilerBuild` option for the client generator block in `schema.prisma` with two options: `fast` and `small`. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade-off for speed). By default, the `fast` mode is used, but this can be set by the user. We still have more in progress for performance, but this new `compilerBuild` option is our first step toward addressing your concerns! ```text @@ -24,13 +24,13 @@ generator client { } ``` -- [\#29005](https://github.com/prisma/prisma/pull/29005): Bypass the Query Compiler for Raw Queries +- [\#29005](https://github.com/prisma/orm/pull/29005): Bypass the Query Compiler for Raw Queries Raw queries (`$executeRaw`, `$queryRaw`) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead. -- [\#28965](https://github.com/prisma/prisma/pull/28965): Update MSSQL to v12.2.0 +- [\#28965](https://github.com/prisma/orm/pull/28965): Update MSSQL to v12.2.0 This community PR updates the `@prisma/adapter-mssql` to use MSSQL v12.2.0. Thanks [Jay-Lokhande](https://github.com/Jay-Lokhande)! -- [\#29001](https://github.com/prisma/prisma/pull/29001): Pin better-sqlite3 version to avoid SQLite bug +- [\#29001](https://github.com/prisma/orm/pull/29001): Pin better-sqlite3 version to avoid SQLite bug An underlying bug in SQLite 3.51.0 has affected the `better-sqlite3` adapter. We’ve bumped the version that powers `@prisma/better-sqlite3` and have pinned the version to prevent any unexpected issues. If you are using `@prisma/better-sqlite3` , please upgrade to v7.3.0. -- [\#29002](https://github.com/prisma/prisma/pull/29002): Revert `@map` enums to v6.19.0 behavior +- [\#29002](https://github.com/prisma/orm/pull/29002): Revert `@map` enums to v6.19.0 behavior In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the `@map` function. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion. - [prisma-engines\#5745](https://github.com/prisma/prisma-engines/pull/5745): Cast BigInt to text in JSON aggregation When using `relationJoins` with BigInt fields in Prisma 7, JavaScript's `JSON.parse` loses precision for integers larger than `Number.MAX_SAFE_INTEGER` (2^53 - 1).This happens because PostgreSQL's `JSONB_BUILD_OBJECT` returns BigInt values as JSON numbers, which JavaScript cannot represent precisely. diff --git a/apps/site/content/changelog/2026-02-11.mdx b/apps/site/content/changelog/2026-02-11.mdx index ae76613056..0914b0b806 100644 --- a/apps/site/content/changelog/2026-02-11.mdx +++ b/apps/site/content/changelog/2026-02-11.mdx @@ -83,9 +83,9 @@ This release also includes a set of fixes from Prisma and community contributors - [prisma-engines#5767](https://github.com/prisma/prisma-engines/pull/5767): Fixed PostgreSQL migration scripts to allow `CREATE INDEX CONCURRENTLY` - [prisma-engines#5752](https://github.com/prisma/prisma-engines/pull/5752): Fixed BigInt precision loss in JSON aggregation for MySQL and CockroachDB - [prisma-engines#5750](https://github.com/prisma/prisma-engines/pull/5750): Fixed connection failures with non-ASCII database names -- [#29155](https://github.com/prisma/prisma/pull/29155): Fixed silent transaction commit errors in the PlanetScale adapter -- [#29141](https://github.com/prisma/prisma/pull/29141): Resolved SQL Server adapter race condition errors during commit and rollback -- [#29158](https://github.com/prisma/prisma/pull/29158): Fixed MSSQL connection string parsing for passwords with curly braces +- [#29155](https://github.com/prisma/orm/pull/29155): Fixed silent transaction commit errors in the PlanetScale adapter +- [#29141](https://github.com/prisma/orm/pull/29141): Resolved SQL Server adapter race condition errors during commit and rollback +- [#29158](https://github.com/prisma/orm/pull/29158): Fixed MSSQL connection string parsing for passwords with curly braces ## Enterprise support diff --git a/apps/site/content/changelog/2026-02-19.mdx b/apps/site/content/changelog/2026-02-19.mdx index 4ff02c3278..44edcb3cd7 100644 --- a/apps/site/content/changelog/2026-02-19.mdx +++ b/apps/site/content/changelog/2026-02-19.mdx @@ -19,16 +19,16 @@ Prisma ORM v7.4.1 is a patch release focused on bug fixes and quality improvemen **Prisma Client** -- [#29184](https://github.com/prisma/prisma/pull/29184): Fix cursor-based pagination regression with parameterized values -- [#29198](https://github.com/prisma/prisma/pull/29198): Preserve `Prisma.skip` through query extension argument cloning -- [#25571](https://github.com/prisma/prisma/pull/25571): Enable batching of multiple queries inside interactive transactions -- [#29182](https://github.com/prisma/prisma/pull/29182): Add missing JSON value deserialization for JSONB parameter fields -- [#29218](https://github.com/prisma/prisma/pull/29218): Apply result extensions correctly for nested and fluent relations +- [#29184](https://github.com/prisma/orm/pull/29184): Fix cursor-based pagination regression with parameterized values +- [#29198](https://github.com/prisma/orm/pull/29198): Preserve `Prisma.skip` through query extension argument cloning +- [#25571](https://github.com/prisma/orm/pull/25571): Enable batching of multiple queries inside interactive transactions +- [#29182](https://github.com/prisma/orm/pull/29182): Add missing JSON value deserialization for JSONB parameter fields +- [#29218](https://github.com/prisma/orm/pull/29218): Apply result extensions correctly for nested and fluent relations - [prisma-engines#5777](https://github.com/prisma/prisma-engines/pull/5777): Allow missing config datasource URL and validate only when needed **Driver Adapters** -- [#29192](https://github.com/prisma/prisma/pull/29192): `@prisma/adapter-ppg` now handles null values in type parsers for nullable columns +- [#29192](https://github.com/prisma/orm/pull/29192): `@prisma/adapter-ppg` now handles null values in type parsers for nullable columns **Prisma Schema Language** diff --git a/apps/site/content/changelog/2026-02-27.mdx b/apps/site/content/changelog/2026-02-27.mdx index 68b8306666..640c709cd3 100644 --- a/apps/site/content/changelog/2026-02-27.mdx +++ b/apps/site/content/changelog/2026-02-27.mdx @@ -19,16 +19,16 @@ Prisma ORM v7.4.2 is a patch release focused on bug fixes and quality improvemen **Prisma Client** -- [#29243](https://github.com/prisma/prisma/pull/29243): Fix a case-insensitive `IN` and `NOT IN` filter regression -- [#29262](https://github.com/prisma/prisma/pull/29262): Fix a query plan mutation issue that resulted in broken cursor queries +- [#29243](https://github.com/prisma/orm/pull/29243): Fix a case-insensitive `IN` and `NOT IN` filter regression +- [#29262](https://github.com/prisma/orm/pull/29262): Fix a query plan mutation issue that resulted in broken cursor queries - [prisma-engines#5784](https://github.com/prisma/prisma-engines/pull/5784): Fix an array parameter wrapping issue in push operations -- [#29268](https://github.com/prisma/prisma/pull/29268): Fix `Uint8Array` serialization in nested JSON fields -- [#29251](https://github.com/prisma/prisma/pull/29251): Fix an issue with MySQL joins that relied on non-strict equality +- [#29268](https://github.com/prisma/orm/pull/29268): Fix `Uint8Array` serialization in nested JSON fields +- [#29251](https://github.com/prisma/orm/pull/29251): Fix an issue with MySQL joins that relied on non-strict equality **Driver Adapters** -- [#29238](https://github.com/prisma/prisma/pull/29238): `@prisma/adapter-mariadb` now checks for a binary collation when detecting text columns -- [#29246](https://github.com/prisma/prisma/pull/29246): Correct `relationJoins` compatibility checks for MariaDB 8.x versions +- [#29238](https://github.com/prisma/orm/pull/29238): `@prisma/adapter-mariadb` now checks for a binary collation when detecting text columns +- [#29246](https://github.com/prisma/orm/pull/29246): Correct `relationJoins` compatibility checks for MariaDB 8.x versions **Schema Engine** diff --git a/apps/site/content/changelog/2026-03-11.mdx b/apps/site/content/changelog/2026-03-11.mdx index 6757ab19a4..54c4d83f3e 100644 --- a/apps/site/content/changelog/2026-03-11.mdx +++ b/apps/site/content/changelog/2026-03-11.mdx @@ -21,20 +21,20 @@ Prisma ORM v7.5.0 adds support for nested transaction rollback behavior for SQL This lets Prisma track transaction ID and nesting depth so it can reuse an existing open transaction in the underlying engine. It also enables using `$transaction` from an interactive transaction client while making sure inner nested transactions are rolled back when the outer transaction fails. -- [#21678](https://github.com/prisma/prisma/pull/21678): Added support for nested transaction rollbacks via savepoints +- [#21678](https://github.com/prisma/orm/pull/21678): Added support for nested transaction rollbacks via savepoints ### Bug fixes **Driver Adapters** -- [#29285](https://github.com/prisma/prisma/pull/29285): `adapter-mariadb` now uses the binary MySQL protocol to fix lossy number conversions -- [#29277](https://github.com/prisma/prisma/pull/29277): Made `@types/pg` a direct dependency of `adapter-pg` for a better TypeScript experience +- [#29285](https://github.com/prisma/orm/pull/29285): `adapter-mariadb` now uses the binary MySQL protocol to fix lossy number conversions +- [#29277](https://github.com/prisma/orm/pull/29277): Made `@types/pg` a direct dependency of `adapter-pg` for a better TypeScript experience **Prisma Client** -- [#29286](https://github.com/prisma/prisma/pull/29286): Resolved `Prisma.DbNull` serializing as an empty object in some bundled environments like Next.js -- [#29274](https://github.com/prisma/prisma/pull/29274): Fixed DateTime fields returning `Invalid Date` with `unixepoch-ms` timestamps in some cases -- [#29327](https://github.com/prisma/prisma/pull/29327): Fixed a cursor-based pagination issue with `@db.Date` columns +- [#29286](https://github.com/prisma/orm/pull/29286): Resolved `Prisma.DbNull` serializing as an empty object in some bundled environments like Next.js +- [#29274](https://github.com/prisma/orm/pull/29274): Fixed DateTime fields returning `Invalid Date` with `unixepoch-ms` timestamps in some cases +- [#29327](https://github.com/prisma/orm/pull/29327): Fixed a cursor-based pagination issue with `@db.Date` columns **Schema Engine** diff --git a/apps/site/content/changelog/2026-03-27.mdx b/apps/site/content/changelog/2026-03-27.mdx index 0eaf75b8dd..b7ea3b2aa9 100644 --- a/apps/site/content/changelog/2026-03-27.mdx +++ b/apps/site/content/changelog/2026-03-27.mdx @@ -20,33 +20,33 @@ source: **CLI** -- [#29352](https://github.com/prisma/prisma/pull/29352): Added a new `prisma postgres link` command that connects a local project to a Prisma Postgres database. +- [#29352](https://github.com/prisma/orm/pull/29352): Added a new `prisma postgres link` command that connects a local project to a Prisma Postgres database. This is the first command in a new `prisma postgres` command group for managing Prisma Postgres databases directly from the CLI. **Driver Adapters** -- [#29395](https://github.com/prisma/prisma/pull/29395): `@prisma/adapter-pg` adds a `statementNameGenerator` option for custom prepared statement naming and `pg` statement caching -- [#29287](https://github.com/prisma/prisma/pull/29287): `@prisma/adapter-pg` now supports passing connection strings directly to the constructor -- [#29392](https://github.com/prisma/prisma/pull/29392): `@prisma/adapter-mariadb` adds a `useTextProtocol` option to toggle between text and binary protocols +- [#29395](https://github.com/prisma/orm/pull/29395): `@prisma/adapter-pg` adds a `statementNameGenerator` option for custom prepared statement naming and `pg` statement caching +- [#29287](https://github.com/prisma/orm/pull/29287): `@prisma/adapter-pg` now supports passing connection strings directly to the constructor +- [#29392](https://github.com/prisma/orm/pull/29392): `@prisma/adapter-mariadb` adds a `useTextProtocol` option to toggle between text and binary protocols ### Bug fixes **Prisma Client** -- [#29382](https://github.com/prisma/prisma/pull/29382): Disabled caching of `createMany` queries to avoid cache bloat and potential Node.js crashes in bulk operations -- [#28724](https://github.com/prisma/prisma/pull/28724): Made `NowGenerator` lazy to avoid synchronous `new Date()` calls, fixing Next.js dynamic usage errors in cached components -- [#29346](https://github.com/prisma/prisma/pull/29346): Fixed missing export of `Get GroupByPayload` type in the new `prisma-client` generator +- [#29382](https://github.com/prisma/orm/pull/29382): Disabled caching of `createMany` queries to avoid cache bloat and potential Node.js crashes in bulk operations +- [#28724](https://github.com/prisma/orm/pull/28724): Made `NowGenerator` lazy to avoid synchronous `new Date()` calls, fixing Next.js dynamic usage errors in cached components +- [#29346](https://github.com/prisma/orm/pull/29346): Fixed missing export of `Get GroupByPayload` type in the new `prisma-client` generator **CLI** -- [#29377](https://github.com/prisma/prisma/pull/29377): Added streaming parsing with automatic fallback for very large Prisma schemas that can hit V8 string limits +- [#29377](https://github.com/prisma/orm/pull/29377): Added streaming parsing with automatic fallback for very large Prisma schemas that can hit V8 string limits **Driver Adapters** -- [#29390](https://github.com/prisma/prisma/pull/29390): Relaxed the `@types/pg` version constraint to `^8.16.0` -- [#29307](https://github.com/prisma/prisma/pull/29307): Corrected `ColumnNotFound` error handling so column names are extracted from both quoted and unquoted PostgreSQL messages -- [#29392](https://github.com/prisma/prisma/pull/29392): Disabled `mariadb` statement caching by default to address a reported leak +- [#29390](https://github.com/prisma/orm/pull/29390): Relaxed the `@types/pg` version constraint to `^8.16.0` +- [#29307](https://github.com/prisma/orm/pull/29307): Corrected `ColumnNotFound` error handling so column names are extracted from both quoted and unquoted PostgreSQL messages +- [#29392](https://github.com/prisma/orm/pull/29392): Disabled `mariadb` statement caching by default to address a reported leak ## Prisma Studio diff --git a/apps/site/content/changelog/2026-04-07.mdx b/apps/site/content/changelog/2026-04-07.mdx index c2c7f1ffc8..2e931f4ade 100644 --- a/apps/site/content/changelog/2026-04-07.mdx +++ b/apps/site/content/changelog/2026-04-07.mdx @@ -31,7 +31,7 @@ It detects the current project state and only runs the steps that are needed: Each side-effecting step prompts for confirmation, and re-running the command skips any steps that are already complete. -This feature shipped in [#29374](https://github.com/prisma/prisma/pull/29374) and [#29424](https://github.com/prisma/prisma/pull/29424). +This feature shipped in [#29374](https://github.com/prisma/orm/pull/29374) and [#29424](https://github.com/prisma/orm/pull/29424). **Basic usage** diff --git a/apps/site/content/changelog/2026-04-22.mdx b/apps/site/content/changelog/2026-04-22.mdx index 862a22f8e3..3c3389b967 100644 --- a/apps/site/content/changelog/2026-04-22.mdx +++ b/apps/site/content/changelog/2026-04-22.mdx @@ -18,10 +18,10 @@ Prisma ORM adds a parameter that sets the query plan cache size. It also fixes J Prisma ORM adds query plan cache tuning and fixes JSON equality and Cloudflare D1 correctness issues. -- **New** · Prisma ORM now accepts a parameter that sets the size of the query plan cache. ([prisma/prisma#29503](https://github.com/prisma/prisma/pull/29503)) +- **New** · Prisma ORM now accepts a parameter that sets the size of the query plan cache. ([prisma/prisma#29503](https://github.com/prisma/orm/pull/29503)) - **Fixed** · Prisma ORM case-insensitive equality on JSON values returns the correct result. ([prisma/prisma-engines#5806](https://github.com/prisma/prisma-engines/pull/5806)) - **Fixed** · Prisma ORM equality checks on JSON list values behave consistently. ([prisma/prisma-engines#5804](https://github.com/prisma/prisma-engines/pull/5804)) -- **Fixed** · The Prisma ORM D1 adapter no longer attempts savepoint operations, which Cloudflare D1 does not support. ([prisma/prisma#29499](https://github.com/prisma/prisma/pull/29499)) +- **Fixed** · The Prisma ORM D1 adapter no longer attempts savepoint operations, which Cloudflare D1 does not support. ([prisma/prisma#29499](https://github.com/prisma/orm/pull/29499)) --- diff --git a/apps/site/content/changelog/2026-04-27.mdx b/apps/site/content/changelog/2026-04-27.mdx index feda53bd1c..eb8b07b3c1 100644 --- a/apps/site/content/changelog/2026-04-27.mdx +++ b/apps/site/content/changelog/2026-04-27.mdx @@ -30,15 +30,15 @@ try { } ``` -Shipped in [prisma/prisma#29512](https://github.com/prisma/prisma/pull/29512). +Shipped in [prisma/prisma#29512](https://github.com/prisma/orm/pull/29512). ## Prisma ORM Prisma ORM fixes MongoDB replica set setup and patches bundled dependencies. -- **Fixed** · Prisma ORM MongoDB replica set initialization is idempotent in the Docker setup, so re-running it no longer errors. ([prisma/prisma#29515](https://github.com/prisma/prisma/pull/29515)) +- **Fixed** · Prisma ORM MongoDB replica set initialization is idempotent in the Docker setup, so re-running it no longer errors. ([prisma/prisma#29515](https://github.com/prisma/orm/pull/29515)) -> **Security:** Prisma ORM updates bundled dependencies (`hono`, `ajv`, `uuid`) to patch known advisories. ([prisma/prisma#29514](https://github.com/prisma/prisma/pull/29514)) +> **Security:** Prisma ORM updates bundled dependencies (`hono`, `ajv`, `uuid`) to patch known advisories. ([prisma/prisma#29514](https://github.com/prisma/orm/pull/29514)) --- diff --git a/apps/site/content/changelog/2026-05-19.mdx b/apps/site/content/changelog/2026-05-19.mdx index 3b73ebcabe..4e314f3665 100644 --- a/apps/site/content/changelog/2026-05-19.mdx +++ b/apps/site/content/changelog/2026-05-19.mdx @@ -18,7 +18,7 @@ Prisma ORM no longer calls the deprecated `Buffer()` constructor, so recent Node Prisma ORM removes a deprecated Node.js API call. -- **Fixed** · Prisma ORM no longer calls the deprecated `Buffer()` constructor, clearing the `DEP0005` deprecation warning it raised on recent Node.js versions. ([prisma/prisma#29538](https://github.com/prisma/prisma/pull/29538)) +- **Fixed** · Prisma ORM no longer calls the deprecated `Buffer()` constructor, clearing the `DEP0005` deprecation warning it raised on recent Node.js versions. ([prisma/prisma#29538](https://github.com/prisma/orm/pull/29538)) --- diff --git a/apps/site/content/changelog/2026-06-05.mdx b/apps/site/content/changelog/2026-06-05.mdx index ec10f3a665..9219e3906a 100644 --- a/apps/site/content/changelog/2026-06-05.mdx +++ b/apps/site/content/changelog/2026-06-05.mdx @@ -56,8 +56,8 @@ Prisma Studio makes query details copyable and fixes SQL view schema selection. Prisma ORM speeds up type-checking and tightens credential storage. -- **Improved** · Prisma ORM type-checking is faster on large generated client types. ([prisma/prisma#29592](https://github.com/prisma/prisma/pull/29592)) -- **Improved** · Prisma ORM stored platform auth credentials now use stricter file permissions. ([prisma/prisma#29568](https://github.com/prisma/prisma/pull/29568)) +- **Improved** · Prisma ORM type-checking is faster on large generated client types. ([prisma/prisma#29592](https://github.com/prisma/orm/pull/29592)) +- **Improved** · Prisma ORM stored platform auth credentials now use stricter file permissions. ([prisma/prisma#29568](https://github.com/prisma/orm/pull/29568)) --- diff --git a/apps/site/content/changelog/2026-06-11.mdx b/apps/site/content/changelog/2026-06-11.mdx index 4a198059b1..6fab1f6b01 100644 --- a/apps/site/content/changelog/2026-06-11.mdx +++ b/apps/site/content/changelog/2026-06-11.mdx @@ -64,7 +64,7 @@ Prisma 8 adds transaction grouping on the SQLite facade. Prisma ORM ships more specific error messages for driver adapters. -- **Improved** · Prisma ORM driver adapter errors now carry more specific messages. ([prisma/prisma#29624](https://github.com/prisma/prisma/pull/29624)) +- **Improved** · Prisma ORM driver adapter errors now carry more specific messages. ([prisma/prisma#29624](https://github.com/prisma/orm/pull/29624)) ## Guides and articles diff --git a/apps/site/content/changelog/2026-07-09.mdx b/apps/site/content/changelog/2026-07-09.mdx index 5ea23c6a4e..437696f4e5 100644 --- a/apps/site/content/changelog/2026-07-09.mdx +++ b/apps/site/content/changelog/2026-07-09.mdx @@ -50,7 +50,7 @@ Prisma 8 reads external enum types as typed unions and tightens contract inferen Prisma ORM removes a destructive agent-facing tool and surfaces the `typedSql` preview feature. -- **Improved** · The Prisma MCP server no longer exposes a `migrate-reset` tool. An agent that needs a reset must run `prisma migrate reset` through the CLI, where the safety checkpoint requires explicit confirmation before the database is dropped. ([prisma/prisma#29691](https://github.com/prisma/prisma/pull/29691)) +- **Improved** · The Prisma MCP server no longer exposes a `migrate-reset` tool. An agent that needs a reset must run `prisma migrate reset` through the CLI, where the safety checkpoint requires explicit confirmation before the database is dropped. ([prisma/prisma#29691](https://github.com/prisma/orm/pull/29691)) - **Improved** · The `typedSql` preview feature now appears in language-tool autocomplete and in schema validation error suggestions. It was already fully functional when enabled explicitly. ([prisma/prisma-engines#5836](https://github.com/prisma/prisma-engines/pull/5836)) --- diff --git a/apps/site/content/changelog/2026-07-17.mdx b/apps/site/content/changelog/2026-07-17.mdx index 947dd5310f..6d41b7cb9e 100644 --- a/apps/site/content/changelog/2026-07-17.mdx +++ b/apps/site/content/changelog/2026-07-17.mdx @@ -99,13 +99,13 @@ The Prisma Console adds a workspace support portal. Prisma ORM closes a gap in its AI agent safety checkpoint. -- **Improved** · `prisma db push --accept-data-loss` now runs the AI safety confirmation checkpoint before applying a destructive schema push, the same checkpoint `--force-reset` already used. An AI agent can no longer opt into data loss without explicit user consent. ([prisma/prisma#29713](https://github.com/prisma/prisma/pull/29713)) +- **Improved** · `prisma db push --accept-data-loss` now runs the AI safety confirmation checkpoint before applying a destructive schema push, the same checkpoint `--force-reset` already used. An AI agent can no longer opt into data loss without explicit user consent. ([prisma/prisma#29713](https://github.com/prisma/orm/pull/29713)) ## Prisma Studio Prisma Studio 0.33.0 is now bundled in the Prisma CLI. -- **Improved** · The Prisma CLI now bundles Prisma Studio 0.33.0, which includes the new Migrations view, and no longer prints aborted-response errors when a Prisma Studio tab closes mid-request. ([prisma/prisma#29720](https://github.com/prisma/prisma/pull/29720)) +- **Improved** · The Prisma CLI now bundles Prisma Studio 0.33.0, which includes the new Migrations view, and no longer prints aborted-response errors when a Prisma Studio tab closes mid-request. ([prisma/prisma#29720](https://github.com/prisma/orm/pull/29720)) ## Fixes and improvements @@ -118,8 +118,8 @@ Prisma Studio 0.33.0 is now bundled in the Prisma CLI. **Prisma ORM** -- **Fixed** · An invalid `Date` passed to `$queryRaw` or `$executeRaw` now raises a validation error instead of being silently sent to the database as the string `"null"`. ([prisma/prisma#29697](https://github.com/prisma/prisma/pull/29697)) -- **Fixed** · Query masking in error reports now masks each quoted string independently, so a list like `name_in: ["a", "b", "c"]` no longer collapses into a single masked value. ([prisma/prisma#29723](https://github.com/prisma/prisma/pull/29723)) +- **Fixed** · An invalid `Date` passed to `$queryRaw` or `$executeRaw` now raises a validation error instead of being silently sent to the database as the string `"null"`. ([prisma/prisma#29697](https://github.com/prisma/orm/pull/29697)) +- **Fixed** · Query masking in error reports now masks each quoted string independently, so a list like `name_in: ["a", "b", "c"]` no longer collapses into a single masked value. ([prisma/prisma#29723](https://github.com/prisma/orm/pull/29723)) - **Fixed** · Prisma Migrate now renders constraint renames as separate SQL statements. ([prisma/prisma-engines#4906](https://github.com/prisma/prisma-engines/pull/4906)) **Prisma Studio** diff --git a/apps/site/next.config.mjs b/apps/site/next.config.mjs index 4a2568a592..37a33a627a 100644 --- a/apps/site/next.config.mjs +++ b/apps/site/next.config.mjs @@ -519,7 +519,7 @@ const config = { { permanent: true, source: "/blog/mongodb-preview-ow4wahkekaep", - destination: "https://github.com/prisma/prisma/issues/1277", + destination: "https://github.com/prisma/orm/issues/1277", }, { permanent: true, diff --git a/apps/site/public/.well-known/security.txt b/apps/site/public/.well-known/security.txt index 910b03f24a..901e564099 100644 --- a/apps/site/public/.well-known/security.txt +++ b/apps/site/public/.well-known/security.txt @@ -2,4 +2,4 @@ Contact: mailto:security@prisma.io Expires: 2027-04-28T00:00:00Z Preferred-Languages: en Canonical: https://www.prisma.io/.well-known/security.txt -Policy: https://github.com/prisma/prisma/security/policy +Policy: https://github.com/prisma/orm/security/policy diff --git a/apps/site/src/app/community/page.tsx b/apps/site/src/app/community/page.tsx index eb3e62533c..b0e25f5edc 100644 --- a/apps/site/src/app/community/page.tsx +++ b/apps/site/src/app/community/page.tsx @@ -64,20 +64,20 @@ const CONTRIBUTING = [ title: "Open an issue", description: "Found a bug or have a feature request? Open an issue on the Prisma GitHub repository.", - link: "https://github.com/prisma/prisma/issues", + link: "https://github.com/prisma/orm/issues", cta: "Open issue", }, { title: "Join the discussion", description: "Ask questions, share ideas, and connect with the Prisma team on GitHub Discussions.", - link: "https://github.com/prisma/prisma/discussions", + link: "https://github.com/prisma/orm/discussions", cta: "Start discussion", }, { title: "Contributing guide", description: "Learn how to contribute code, docs, and improvements to the Prisma project.", - link: "https://github.com/prisma/prisma/blob/main/CONTRIBUTING.md", + link: "https://github.com/prisma/orm/blob/main/CONTRIBUTING.md", cta: "Read guide", }, ]; diff --git a/apps/site/src/app/support-policy/page.tsx b/apps/site/src/app/support-policy/page.tsx index 6562f8b836..2411123089 100644 --- a/apps/site/src/app/support-policy/page.tsx +++ b/apps/site/src/app/support-policy/page.tsx @@ -98,9 +98,9 @@ export default function SupportPolicyPage() {

Support for Prisma's open-source software, including{" "} - Prisma ORM, is provided through our + Prisma ORM, is provided through our community channels on{" "} - GitHub and{" "} + GitHub and{" "} Discord.

diff --git a/apps/site/src/app/support/page.tsx b/apps/site/src/app/support/page.tsx index 60192b0558..0eafdea17b 100644 --- a/apps/site/src/app/support/page.tsx +++ b/apps/site/src/app/support/page.tsx @@ -30,11 +30,11 @@ const SUPPORT_CARDS: SupportCard[] = [ links: [ { label: "Report a bug", - url: "https://github.com/prisma/prisma/issues/new?assignees=&labels=&template=bug_report.md", + url: "https://github.com/prisma/orm/issues/new?assignees=&labels=&template=bug_report.md", }, { label: "Request a new feature", - url: "https://github.com/prisma/prisma/issues/new?assignees=&labels=&template=feature_request.md", + url: "https://github.com/prisma/orm/issues/new?assignees=&labels=&template=feature_request.md", }, ], }, diff --git a/apps/site/src/components/product/content/orm.ts b/apps/site/src/components/product/content/orm.ts index 659e8f133a..5769a336df 100644 --- a/apps/site/src/components/product/content/orm.ts +++ b/apps/site/src/components/product/content/orm.ts @@ -18,7 +18,7 @@ import type { ProductPageContent } from "../types"; // - The features and integrations carry no "Learn more" destinations, so none // are rendered rather than invented. -const GITHUB = "https://github.com/prisma/prisma"; +const GITHUB = "https://github.com/prisma/orm"; const DOCS = "/docs"; export const ormContent: ProductPageContent = { diff --git a/apps/site/src/components/sections/contact-support.tsx b/apps/site/src/components/sections/contact-support.tsx index afa9d0e11d..4266da882a 100644 --- a/apps/site/src/components/sections/contact-support.tsx +++ b/apps/site/src/components/sections/contact-support.tsx @@ -21,7 +21,7 @@ const CHANNELS = [ name: "Bugs and feature requests", Icon: Github, description: "Report a bug or request a feature on GitHub.", - cta: { label: "Open GitHub", href: "https://github.com/prisma/prisma/issues" }, + cta: { label: "Open GitHub", href: "https://github.com/prisma/orm/issues" }, }, ]; diff --git a/apps/site/src/data/support.json b/apps/site/src/data/support.json index f986ec825f..89d30a9c05 100644 --- a/apps/site/src/data/support.json +++ b/apps/site/src/data/support.json @@ -9,12 +9,12 @@ "links": [ { "label": "Report a bug", - "url": "https://github.com/prisma/prisma/issues/new?assignees=&labels=&template=bug_report.md", + "url": "https://github.com/prisma/orm/issues/new?assignees=&labels=&template=bug_report.md", "icon": "fa-brands fa-github" }, { "label": "Request a new feature", - "url": "https://github.com/prisma/prisma/issues/new?assignees=&labels=&template=feature_request.md", + "url": "https://github.com/prisma/orm/issues/new?assignees=&labels=&template=feature_request.md", "icon": "fa-brands fa-github" } ]