We upgraded to

v3.11.0

from

v2.27.0

using Postgres and we just created our first migration file using

npx prisma migrate dev --name test_migration_file --create-only

and we are noticing a ton of changes that seem to drop all foreign key constraints and re-add them. Is this typical? Is this a cause of the version upgrade?

you might want to try

db pull

to see if there's stuff like constraint names etc.

nothing seemed to change from the

db pull

besides a reorganization of the

schema.prisma

I have a feeling the new referential stuff https://www.prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3/referential-actions casues the constraints to be changed

so pulling with the 3.x should give you the referential actions and constraint names to your schema

hmm that didnt happen, though it looks like

cascade

is the default which is fine for everything for us