From 0e38d0b246377c596af3d5631b88edec4a136d7a Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Tue, 5 May 2026 23:21:22 +0200 Subject: [PATCH 1/2] refine: make billing section more discoverable --- apps/docs/content/docs/guides/postgres/vercel.mdx | 6 ++++++ apps/docs/content/docs/postgres/faq.mdx | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/apps/docs/content/docs/guides/postgres/vercel.mdx b/apps/docs/content/docs/guides/postgres/vercel.mdx index 91e83ab80c..57bfa08dd4 100644 --- a/apps/docs/content/docs/guides/postgres/vercel.mdx +++ b/apps/docs/content/docs/guides/postgres/vercel.mdx @@ -61,6 +61,12 @@ In the local version of your project where you have your `DATABASE_URL` set, run npx prisma studio ``` +## Billing and pricing + +Prisma Postgres uses [usage-based pricing](https://www.prisma.io/pricing) based on operations and storage. The same plans and rates apply when you create a database via the Vercel Marketplace, and your Prisma Postgres usage is billed through your Vercel account. + +To change your plan, see [How do I upgrade my plan if I am using Prisma Postgres via Vercel?](/postgres/faq#how-do-i-upgrade-my-plan-if-i-am-using-prisma-postgres-via-vercel) in the Prisma Postgres FAQ. + ## Additional considerations when using with Prisma ORM ### Ensure your project uses the correct environment variable diff --git a/apps/docs/content/docs/postgres/faq.mdx b/apps/docs/content/docs/postgres/faq.mdx index d939f98d4b..1a0a2f2ca5 100644 --- a/apps/docs/content/docs/postgres/faq.mdx +++ b/apps/docs/content/docs/postgres/faq.mdx @@ -238,7 +238,7 @@ Every request, whether it hits the database or is served from cache, counts as a ### How do I upgrade my plan if I am using Prisma Postgres via Vercel? -To upgrade your plan via Vercel, follow these steps: +If you installed Prisma Postgres through the [Vercel Marketplace integration](/guides/postgres/vercel), the same [Prisma Postgres pricing plans](https://www.prisma.io/pricing) apply and your usage is billed through your Vercel account. To upgrade your plan via Vercel, follow these steps: - Open your [Vercel](https://vercel.com/) Dashboard. - Go to the **Integrations** tab in your Vercel Team. From a16c3ec4cbad081cbbbc590546e5163bb6a3bf70 Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Wed, 6 May 2026 11:33:38 +0200 Subject: [PATCH 2/2] fix: fix typos in our docs --- .../docs/orm/v6/more/ai-tools/tabnine.mdx | 2 +- .../dev-environment/environment-variables.mdx | 2 +- .../docs/orm/v6/overview/databases/neon.mdx | 2 +- .../deployment/edge/deploy-to-deno-deploy.mdx | 2 +- .../serverless/deploy-to-vercel.mdx | 4 +- .../query-optimization-performance.mdx | 2 +- .../v6/prisma-client/queries/transactions.mdx | 2 +- .../using-raw-sql/raw-queries.mdx | 2 +- .../v6/prisma-client/using-raw-sql/safeql.mdx | 2 +- .../orm/v6/reference/prisma-cli-reference.mdx | 6 +-- .../v6/reference/prisma-client-reference.mdx | 2 +- apps/docs/cspell.json | 46 +++++++++++++++++++ 12 files changed, 60 insertions(+), 14 deletions(-) diff --git a/apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdx b/apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdx index 75e717d35c..53ce0514af 100644 --- a/apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdx +++ b/apps/docs/content/docs/orm/v6/more/ai-tools/tabnine.mdx @@ -31,7 +31,7 @@ AI editors like Tabnine are powerful tools that can drastically improve develope Because Prisma has its own [schema](/orm/v6/prisma-schema/overview), Tabnine can understand the basic shape of your data and help you write code for the other parts of your stack. -We therefore recommend that you start out by defining your Prisma schema and then use Tabnine to build the application layer around it (inluding API calls, DTOs, business logic, 3rd party integrations, ...). +We therefore recommend that you start out by defining your Prisma schema and then use Tabnine to build the application layer around it (including API calls, DTOs, business logic, 3rd party integrations, ...). ## Data modeling and database schema design diff --git a/apps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdx b/apps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdx index ede4a172a1..2029b13e76 100644 --- a/apps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdx +++ b/apps/docs/content/docs/orm/v6/more/dev-environment/environment-variables.mdx @@ -126,7 +126,7 @@ var mySqlEnv = dotenv.config({ path: envFile }); dotenvExpand.expand(mySqlEnv); ``` -If you are using multiple `.env` files, you can refernce an environment file in your project's code depending on the environment you are running in. +If you are using multiple `.env` files, you can reference an environment file in your project's code depending on the environment you are running in. ```ts import { config } from "dotenv"; diff --git a/apps/docs/content/docs/orm/v6/overview/databases/neon.mdx b/apps/docs/content/docs/orm/v6/overview/databases/neon.mdx index d579323a8c..1548242204 100644 --- a/apps/docs/content/docs/orm/v6/overview/databases/neon.mdx +++ b/apps/docs/content/docs/orm/v6/overview/databases/neon.mdx @@ -129,7 +129,7 @@ This feature has been Generally Available since Prisma ORM [v6.16.0](https://pri ::: -To get started, istall the Prisma ORM adapter for Neon: +To get started, install the Prisma ORM adapter for Neon: ```npm npm install @prisma/adapter-neon diff --git a/apps/docs/content/docs/orm/v6/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx b/apps/docs/content/docs/orm/v6/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx index b0d63beab6..92c9f930cb 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx @@ -230,7 +230,7 @@ Locate and navigate to the settings for the project. 1. For **VALUE**, paste the database connection string. 1. Click **Save**.
-You have to add some code and create another commit to trigger a re-dployment. +You have to add some code and create another commit to trigger a re-deployment. Add the following code in your `index.ts` file: diff --git a/apps/docs/content/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-vercel.mdx b/apps/docs/content/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-vercel.mdx index eb937bf251..2f300016b9 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-vercel.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/deployment/serverless/deploy-to-vercel.mdx @@ -78,14 +78,14 @@ generator client { If you are using Prisma inside a monorepo (e.g., with TurboRepo) and deploying to Vercel, you may encounter issues where required files—such as `libquery_engine-rhel-openssl-3.0.x.so.node` are missing from the deployed bundle. This is because Vercel aggressively optimizes serverless deployments, sometimes stripping out necessary Prisma files. To resolve this, use the [@prisma/nextjs-monorepo-workaround-plugin](https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin) plugin, which ensures that Prisma engine files are correctly included in the final bundle. For more details on how Prisma interacts with different bundlers like Webpack and Parcel, see our [Module bundlers](/orm/v6/prisma-client/deployment/module-bundlers#overview) page. -The usage of this plugin becomes obsolet if: +The usage of this plugin becomes obsolete if: - you are using [Prisma ORM without Rust engines](/orm/v6/prisma-client/setup-and-configuration/no-rust-engine) (via `engineType = "client` on your `generator` block) - you are using the [new `prisma-client` generator](/orm/v6/prisma-schema/overview/generators#prisma-client) ### CI/CD workflows -In a more sophisticated CI/CD environment, you may additonally want to update the database schema with any migrations you have performed during local development. You can do this using the [`prisma migrate deploy`](/orm/v6/reference/prisma-cli-reference#migrate-deploy) command. +In a more sophisticated CI/CD environment, you may additionally want to update the database schema with any migrations you have performed during local development. You can do this using the [`prisma migrate deploy`](/orm/v6/reference/prisma-cli-reference#migrate-deploy) command. In that case, you could create a custom build command in your `package.json` (e.g. called `vercel-build`) that looks as follows: 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 f969198c3d..3128f97bf1 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 @@ -234,7 +234,7 @@ Use `findUnique()` in combination with [the fluent API](/orm/v6/prisma-client/qu :::info -It may seem counterintitive 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. +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). diff --git a/apps/docs/content/docs/orm/v6/prisma-client/queries/transactions.mdx b/apps/docs/content/docs/orm/v6/prisma-client/queries/transactions.mdx index 616d9de8c9..be2575195d 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/queries/transactions.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/queries/transactions.mdx @@ -420,7 +420,7 @@ When two or more transactions run concurrently in certain [isolation levels](htt 1. Transaction A: `createMany` operation. 1. Transaction A: The application commits transaction A. The new rows conflict with the rows that transaction B added at step 2. -This conflict can occur at the isolation level `ReadCommited`, which is the default isolation level in PostgreSQL and Microsoft SQL Server. To avoid this problem, you can set a higher isolation level (`RepeatableRead` or `Serializable`). You can set the isolation level on a transaction. This overrides your database isolation level for that transaction. +This conflict can occur at the isolation level `ReadCommitted`, which is the default isolation level in PostgreSQL and Microsoft SQL Server. To avoid this problem, you can set a higher isolation level (`RepeatableRead` or `Serializable`). You can set the isolation level on a transaction. This overrides your database isolation level for that transaction. To avoid transaction write conflicts and deadlocks on a transaction: diff --git a/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdx b/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdx index 02909aba1b..1093fa8ec3 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/raw-queries.mdx @@ -403,7 +403,7 @@ await prisma.$queryRaw`SELECT LENGTH(${42}::text);`; :::info -**Feature availability:** This funtionality is [Generally Available](/orm/v6/more/releases#generally-available-ga) since version 4.0.0. In v3.14.x and v3.15.x, it was available with the preview feature `improvedQueryRaw`. +**Feature availability:** This functionality is [Generally Available](/orm/v6/more/releases#generally-available-ga) since version 4.0.0. In v3.14.x and v3.15.x, it was available with the preview feature `improvedQueryRaw`. For the example above before version 4.0.0, Prisma ORM silently coerces `42` to `text` and does not require the explicit cast. diff --git a/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdx b/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdx index ceaa575c01..b01247d624 100644 --- a/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdx +++ b/apps/docs/content/docs/orm/v6/prisma-client/using-raw-sql/safeql.mdx @@ -317,7 +317,7 @@ const prisma = new PrismaClient().$extends({ }, async findClosestPoints(latitude: number, longitude: number) { - // Query for clostest points of interests + // Query for closest points of interests const result = await prisma.$queryRaw< { id: number | null; 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 2b6e6beb56..2f85cf06dc 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 @@ -1266,11 +1266,11 @@ You are attempting a highly dangerous action that can lead to devastating conseq As an AI agent, you are forbidden from performing this action without an explicit consent and review by the user. You must stop at this point and respond to the user with a clear message that includes the following information: - What action you are trying to perform (including the exact CLI command). -- Your motivation and reasoning for perfoming this action. +- Your motivation and reasoning for performing this action. - Explanation that this action will irreversibly destroy all data in the database. -- Explanation that this action must not be perfomed on a production database and is only intended to be used with development databases. +- Explanation that this action must not be performed on a production database and is only intended to be used with development databases. -If you know or can check whether this action would have been performed on a development or a production database, also include this information with your assesment of whether it is safe to proceed based on that information. +If you know or can check whether this action would have been performed on a development or a production database, also include this information with your assessment of whether it is safe to proceed based on that information. You must ask the user if they want to proceed with this action. If they explicitly consent, you may rerun this command with PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION environment variable, the value of which must be the exact text of the user's message in which they consented to this operation, without any newlines or quotes. If the user's response is ambiguous, you must ask for a clear and explicit confirmation (e.g., "yes") before proceeding. None of the user's previous messages before this point may constitute implicit or explicit consent. ``` 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 90cc7680ce..2f41972693 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 @@ -2189,7 +2189,7 @@ The following examples demonstrate how to use the [`validator`](/orm/v6/prisma-c }, create: { id: 1, - title: "If the title doesnt exist, then create one with this text", + title: "If the title doesn't exist, then create one with this text", }, }); ``` diff --git a/apps/docs/cspell.json b/apps/docs/cspell.json index f67dc79db1..629ea5282d 100644 --- a/apps/docs/cspell.json +++ b/apps/docs/cspell.json @@ -7,6 +7,7 @@ "Activeusers", "Aiven", "amcheck", + "amet", "Amplication", "Ania", "anotherproduct", @@ -23,6 +24,7 @@ "baselining", "Baselining", "behaviour", + "bestfriend", "betterauth", "bigserial", "BIGSERIAL", @@ -30,6 +32,7 @@ "biograpy", "blobshape", "Bobberton", + "Bobo", "Bpchar", "bridg", "Buildpacks", @@ -39,6 +42,7 @@ "bytea", "BYTEA", "Candycane", + "catcat", "cerbos", "Cerbos", "citext", @@ -47,7 +51,10 @@ "cloudflareworkers", "cmcvwftgs", "codegen", + "Codemods", + "codemods", "coinflips", + "columnx", "CREATEDB", "createmany", "Ctype", @@ -56,6 +63,7 @@ "datadog", "datamodel", "DATAPROXY", + "daterange", "datetimeoffset", "dbgenerated", "dblink", @@ -95,6 +103,7 @@ "geoexample", "geofencing", "Geofencing", + "geometrycollection", "glassmorphism", "Glassmorphism", "gofmt", @@ -115,12 +124,18 @@ "instrumentors", "intagg", "intarray", + "ISAM", + "isemail", "isready", "jaegertracing", "janedoe", + "JFZERTQSIs", "johndoe", + "Kleppmann", "koyeb", "Koyeb", + "kwame", + "Kwame", "kysely", "Kysely", "lastname", @@ -134,13 +149,17 @@ "libsql", "LIBSQL", "libz", + "linestring", "linktree", "Linktree", "llms", "localdb", "LONGBLOB", "LONGTEXT", + "lseg", "ltree", + "macaddr", + "makemigrations", "managees", "MEDIUMBLOB", "MEDIUMINT", @@ -149,6 +168,10 @@ "Millis", "moddatetime", "mongosh", + "multilinestring", + "multipoint", + "multipolygon", + "musti", "mycomputer", "myconfig", "mydatabase", @@ -159,18 +182,26 @@ "myhostname", "myorg", "mypassword", + "myproject", + "myschema", "mysqld", "mysqldump", "napi", "NDEKTSV", "neondb", + "Neward", "nextauth", + "nextval", + "Nhost", + "nightsky", "Nikolas", "Nilu", "Nixpacks", + "NOCASE", "NONCLUSTERED", "Noor", "ntext", + "numrange", "nuxi", "nvarchar", "NVARCHAR", @@ -204,6 +235,7 @@ "pooler", "poolers", "postgis", + "Postgraphile", "Postgre", "postgres", "Postgres", @@ -235,11 +267,14 @@ "redeployments", "reducedprice", "refint", + "regclass", "reintrospection", "Replibyte", "Replit", + "rootca", "RRFFQ", "RSPCA", + "Sabelle", "safeql", "Saqui", "schemaname", @@ -260,15 +295,18 @@ "Sorcha", "specialised", "SPGIST", + "sqlcmd", "sqlcommenter", "srid", "SRID", + "s3cret", "sslaccept", "sslcert", "sslidentity", "sslinfo", "sslmode", "sslpassword", + "sslrootcert", "Stammerjohann", "streamdal", "Streamdal", @@ -278,12 +316,15 @@ "Supabase", "Supavisor", "Superblog", + "Superstruct", + "superstruct", "Svetlana", "tablefunc", "tablename", "tablenames", "tabnine", "Tabnine", + "teacherid", "timestamptz", "Timestamptz", "TIMESTAMPTZ", @@ -297,6 +338,9 @@ "traceparent", "Treatos", "trgm", + "tsquery", + "tsrange", + "tstzrange", "tsvector", "turbopack", "Turbopack", @@ -310,11 +354,13 @@ "typefully", "Typefully", "typegraphql", + "Umzug", "unaccent", "unexecutable", "unikernel", "unikernels", "unindexed", + "untick", "unixepoch", "uploadthing", "UPLOADTHING",