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
The problem seems to occur only if a field with the same name as the model is used. The (string) value of the field is then replaced with null (related to this operation).
We solved it simply by changing the field name of the relation to the plural form (childs) in order to have a difference to the field name (child).
The text was updated successfully, but these errors were encountered:
dahaupt
added a commit
to dahaupt/prisma-extension-nested-operations
that referenced
this issue
Mar 18, 2024
First of all, thanks a lot for this extension, which is really crucial in our project as part of a multi-tenant validation.
We ran into an issue related to the usage of the Fluent API of Prisma.
Example schema:
Example relation query:
Expected output:
Actual output:
The problem seems to occur only if a field with the same name as the model is used. The (string) value of the field is then replaced with
null
(related to this operation).We solved it simply by changing the field name of the relation to the plural form (
childs
) in order to have a difference to the field name (child
).The text was updated successfully, but these errors were encountered: