From a5f836c9252cab790ec29c87e603db5b42066ecf Mon Sep 17 00:00:00 2001 From: Michael Bagaskoro Edwards <143170516+michael1-0@users.noreply.github.com> Date: Mon, 2 Mar 2026 10:15:56 +0700 Subject: [PATCH 1/2] Clarify db push behavior in Prisma v7 Update documentation to reflect changes in Prisma v7 regarding db push and prisma generate. --- .../orm/prisma-migrate/workflows/prototyping-your-schema.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx index b25b2e8d51..3fef0ae735 100644 --- a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx +++ b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx @@ -11,7 +11,7 @@ The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/orm `db push` uses the same engine as Prisma Migrate to synchronize your Prisma schema with your database schema. The `db push` command: - Introspects the database to infer and executes the changes required to make your database schema reflect the state of your Prisma schema. -- By default, after changes have been applied to the database schema, generators are triggered (for example, Prisma Client). You do not need to manually invoke `prisma generate`. +- In Prisma v7, db push no longer runs prisma generate automatically. Run it explicitly if needed. - If `db push` anticipates that the changes could result in data loss, it will: - Throw an error - Require the `--accept-data-loss` option if you still want to make the changes From 0ea87f519b74fd921f585a00c9478647dc46db4a Mon Sep 17 00:00:00 2001 From: Aman Varshney Date: Tue, 10 Mar 2026 18:15:08 +0530 Subject: [PATCH 2/2] fix(docs): improve db push generate wording Remove redundant version reference since these are already v7 docs. Rephrase to match the style of surrounding bullet points. --- .../orm/prisma-migrate/workflows/prototyping-your-schema.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx index 3fef0ae735..668d5d57ae 100644 --- a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx +++ b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx @@ -11,7 +11,7 @@ The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/orm `db push` uses the same engine as Prisma Migrate to synchronize your Prisma schema with your database schema. The `db push` command: - Introspects the database to infer and executes the changes required to make your database schema reflect the state of your Prisma schema. -- In Prisma v7, db push no longer runs prisma generate automatically. Run it explicitly if needed. +- Does not automatically trigger generators (for example, Prisma Client). You need to manually invoke `prisma generate` after making schema changes. - If `db push` anticipates that the changes could result in data loss, it will: - Throw an error - Require the `--accept-data-loss` option if you still want to make the changes