Skip to content

fix(docs): clarify db push behavior in Prisma v7 #7576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
michael1-0 wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

fix(docs): clarify db push behavior in Prisma v7 #7576

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down