Changes

BREAKING: Specific Input Type for updateMany

We are introducing a specific input type for the updateMany mutation since it does not execute nested mutations. This input type only contains scalar fields. The naming convention is ModelNameUpdateManyMutationInput. This should remove confusion about nested mutations within updateMany being defined in the schema but not executed.
prisma/prisma#3391

Bugfixes

• #3383: A change in the cascading deletes logic. We now do not need to check for loops anymore when executing cascading deletes.
• #3381: We improved the error message during Import when an import field does not match the type defined for it on the data model.