Hi there, i'm pushing to production for first time and have some trouble when doing prisma migrate deploy as my database already contains tables (no conflict in table names) from another project. For now it's not possible to use a separate database in this environment. Is there anyway to make something like "prisma migrate deploy --force" ? Does anyone already have such situations and how did you do in such cases ? Thanks for your replies

You can use

npx prisma db push

to propagate your schema changes. Here are the cases when db push is recommended instead of migrate: db push or migrate

thanks

Hey Jonathan 👋 I would like to clarify that db push command is recommended for quick prototyping and is not generally recommended to be run on production databases. Baselining is an ideal approach which should be used for production databases https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project#baseline-your-production-environment

Hi Nurul, thanks, I finally used baselining 🙂

Amazing!