Alberto Schiabel
Alberto Schiabel
Deprecating this in favor of https://github.com/prisma/prisma/pull/14760 and https://github.com/prisma/prisma/pull/14766.
I can confirm this bug with the current version of Prisma with `referentialIntegrity = prisma`. If we use `referentialIntegrity = foreignKeys`, instead, everything seems to be fine. I have target...
My reproduction above still stands for the following recent Prisma versions: - `4.1.0` - `4.2.0` - `4.2.1`
**Note**: `Error P1012` is considered a `SchemaParserError` according to the [Rust code](https://github.com/prisma/prisma-engines/blob/a3623c31d4eb22f2dccd198738b449488c9b55dd/libs/user-facing-errors/src/common.rs#L182-L186).
Note: `referentialIntegrity: "prisma"` already shows differences w.r.t. `referentialIntegrity: "foreignKeys"`: - `1:1 mandatory (explicit) › [create] child with non existing parent should throw` doesn't throw a foreign key constraint violation error...
This issue has also been reported [here](https://prisma-errors.netlify.app/report/14176). @garrensmith, take this with a grain of salt, but it seems indeed related to [Tiberius](https://github.com/prisma/tiberius/blob/main/src/client/config.rs#L123-L155).
Any news about this PR? @jonathanong
Hi, it's been two years, any update on this PR? @jonathanong @3imed-jaberi @dead-horse @dougwilson
Has any decision been taken on this?
I agree, with @dmitriiivashko and @hauau. @jonathanong, have you created a custom middleware as suggested? If so, can this issue be closed?