We recently upgraded to prisma v3.5.0 from v2.x.x (i want to say like 3 weeks ago) … and today we added a new model to our prisma schema. When we went to run

npm run migrate dev

… the prisma cli ended up creating a pretty confusing / alarming migration. Why is prisma trying to rename existing foreign key and index identifiers? The model we created literally only had two columns so we were expecting a tiny

CREATE TABLE

migration

You're hitting Named Constraints breaking change. Prisma 3 has breaking changes. If you're ok with Prisma default naming, you can just run the migration. Read more for how to upgrade: https://www.prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3 https://www.prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3/named-constraints/

thank you!