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
{{ message }}
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
In other words, if a model only consists of relations to other models, as of now, a findMany call with Prisma Client fails, as by default there has to be some selection set and Prisma Client can't generate one.
Our solution, for now, will be to disable the prisma.MODEL_NAME.ACTION API for that particular model.
The current assumption is, that this is fine for now, as you can always query or mutate that model from one of the sides that it's related to.
In other words, if a model only consists of relations to other models, as of now, a
findMany
call with Prisma Client fails, as by default there has to be some selection set and Prisma Client can't generate one.Our solution, for now, will be to disable the
prisma.MODEL_NAME.ACTION
API for that particular model.The current assumption is, that this is fine for now, as you can always query or mutate that model from one of the sides that it's related to.
This also fixes #530
The text was updated successfully, but these errors were encountered: