Serhii Tatarintsev

Those two packages mismatching could potentially be the culprit. Could you try updating them both to `5.20.0` and rerunning `prisma generate`?

Hey @inhanbyeol , Did you get a chance to have a look at my collegues comment? It'd be helpful for us to move your issue forward. Without further information, we'll...

Hi @rafakwolf Could you please share your schema and the code snippet? Without that information we won't be able to reproduce and fix this issue. Thank you!

Hey @rafakwolf , Did you get a chance to have a look at my previous comment? It'd be helpful for us to move your issue forward. Without further information, we'll...

Hi @Md-Yousuf-sheikh Unfortunately, your code snipped is missing a lot of context needed for us to run it. Could you please provide a bug reproduction in isolated github repository? Thank...

Just so it won't get lost in Slack threads. Right now it breaks tracing tests in prisma/prisma [link](https://github.com/prisma/prisma/actions/runs/9860522768/job/27226978686?pr=24743). Looks like the reason for that is that `itx_query_builder` span got renamed...

I don't think it's a bug, it is an expected behavior. Think of it as of following JS equivalent: ```js admins.filter(admin => { return admin.permissions.every(permission => [1, 2, 3].includes(permission.id)) })...

@jdkdev will something like work for you? ```js prisma.admin.findMany({ where: { permissions: { none: { id: { notIn: [1, 2, 3] } } } } }) ```

@jdkdev that JS code is exactly how this query would behave (I think you meant to have `.includes(permission)` in this case, not `.includes(permission.id)`) with exactly the same behavior described here....

>P.S. If the `every` does what you say it does, how it different from the `some` ? ``` permissions: { every: { id: { in: [1, 2] } } ```...