Hello folks. I’m running into an issue with a sele...
# orm-helph
Hayley Dawson
08/05/2022, 12:44 AMHello folks. I’m running into an issue with a select on a relation. It appears to be the same one as documented here https://github.com/prisma/prisma/discussions/14523 but I cannot find anything on github tracking this as an issue or potential workarounds if it’s related to schema generation. changing our queries wont work for our case we have some generated deeply nested/dynamic items. Any help would be appriciated.
✅ 1
Hayley Dawson
08/05/2022, 12:46 AMI’m wondering if the available types which is empty is part of the issue. Unknown arg
whereselecta
Austin
08/08/2022, 9:41 PMHey Hayley!
If you could share your full Prisma schema and the query you are attempting, I can dig into this further 🙂.
h
Hayley Dawson
08/09/2022, 12:25 AMhey @Austin I figured out the difference its just quite strange to me. If it’s a list, the where clauses sits with the select. of that object. If its not a list, the where clause isn’t an argument and has to sit at a higher level.
Hayley Dawson
08/09/2022, 12:25 AMi’m still trying to make that fly with a dynamic query generator, but it is consistent and digging deep enough to the documentation i did find that seems to match the docs. i wish i wasn’t that way but, wishes aren’t bugs. 🙂
Hayley Dawson
08/09/2022, 12:26 AM(although the higher level docs about clausues and relationships could probably use a link to the more in depth rules of relationships if there isn’t one and i just missed it)
a
Austin
08/09/2022, 3:22 PMAh, that’s interesting. I’ll bring this up internally to see if we can make our docs clearer 👍. Thanks!
👍 1
h
Hayley Dawson
08/09/2022, 3:24 PMnp. tbh if it’s not intentional that non lists cant have a where with their select, that would be very useful to have. at least in our case.