You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why does it sometimes error and sometimes panic?
How is this even possible that the validator sometimes does not catch anything but lets it go to panic?
The text was updated successfully, but these errors were encountered:
As the issues are some time old, we should probably start be reconfirming that the error messages actually still exist this way, and that what was identified back then as the problem of it is still true.
(#1113 for example is internally described as "Panic: Model (probably) has @@id, but Query Engine panics because unsupported" which is very different from how the issue looks like when you click it an read the examples we/I chose in the past)
The problem was, that there was some hardcoded exception in the datamodel validator that was supposed to work together with TS introspection to allow Prisma M2M relation models to pass. It basically let through models without ids if they had two required relation fields.
That was not targeted enough and is also not needed anymore since the Rust introspection does not render models for Prisma M2M relations.
Removing it turns the panics into validation errors as wanted.
Investigate what is going on with ID errors and panics:
#1113
#1083
Why does it sometimes error and sometimes panic?
How is this even possible that the validator sometimes does not catch anything but lets it go to panic?
The text was updated successfully, but these errors were encountered: