I don’t think I value much in this conversation. It is nice to be aware of this, but not really up my alley. I am using DQL in a different kind of way. We are using DQL for some of the more admin side of the aspect to transform data as we change schema around while we build. But my primary use of DQL is multi-level filtering. This is just not possible with a pure GQL endpoint at this time (and possibly never). But, I cannot use strictly DQL, because I need to honor @auth rules. So what do I do? I use DQL to use var blocks and build a filtered set of IDs for the type where I want the filter applied on the GraphQL endpoint. Then I return this set of filtered IDs with a custom query to the client through the GraphQL endpoint and then use this filtered set of IDs to do what would be called an IN(...) clause in other terminology. The GraphQL ignores any id that may not exist, and it filters the ids that do not match the @auth rules. And as suggested above, use @cascade. I have learned to use @cascade many times over as it is a lifesaver.
1 Like