The intent is that the Prisma client is a largely separable product from Prisma migrate. You can use these essentially independently from one another

The prior is just what was built first - and Prisma migrate should be GA relatively soon

(Using "relatively" rather loosely, as they haven't shared any specifics)

I come from knex.js and so each dev can easily create migrations, push to repo, deal with conflicts. We can also easily migrate a prod db up and down in case of any issues.

Are these all things the

prisma migrate

GA version will have?

I guess I’m curious how anyone would be using prisma in production on a project that involves multiple developers.

Skip down to "Lack of rollbacks / Down migrations"

Ok, well aside from that,

prisma migrate deploy --preview-feature

is still technically --preview-feature.

so I should not be using it in production? I guess that’s what you mentioned about people manually running migrations in production earlier?

FWIW basically all it's doing is autogenerating a SQL file for you which you can edit however you want and then run at will

(in production)