Hello prisma folks ! I show up today with an interesting migration question. I've added constraints to my database by creating a migration script manually (some fancy use cases) and for some reason, whenever I try to either

migrate deploy

or

migrate dev

, Prisma fails to do so and attempts to remove my constraints. It works when seeding from scratch, the constraint is picked-up and applied as part of the migration process, but past that whenever creating new migrations or just trying to apply a new one, I get into the same use case. from my understanding, since it's manually added, the schema is unaware of that constraint, but due to the use case of that constraint, I cannot add that to the schema itself. Thoughts ?

Hey, that seems to be a case of Prisma migrate still somehow being aware of the constraint instead of ignoring it (which it should if we do not support it yet). Can you give an example of one of the constraints migrate tries to remove?