# Inability to do simple GraphQL query filtering on node / edges like other GraphQl BaaS'es offer?

**URL:** <https://discuss.dgraph.io/t/inability-to-do-simple-graphql-query-filtering-on-node-edges-like-other-graphql-baases-offer/13417>\
**Category:** Dgraph Cloud / Slash GraphQL\
**Tags:** kind:question\
**Created:** [March 26, 2021, 4:09pm UTC](https://discuss.dgraph.io/t/inability-to-do-simple-graphql-query-filtering-on-node-edges-like-other-graphql-baases-offer/13417 "2021-03-26T16:09:25Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\
**Post date:** [May 20, 2021, 7:31pm UTC](https://discuss.dgraph.io/t/inability-to-do-simple-graphql-query-filtering-on-node-edges-like-other-graphql-baases-offer/13417/18 "2021-05-20T19:31:20Z")

</div>

If you look at the [RFC: Nested Filters in GraphQL - Dev - Discuss Dgraph](http://discuss.hypermode.com/t/rfc-nested-filters-in-graphql/13560?u=amaster507) in progress, they will be using a cascade method as well instead of var blocks last time I reviewed it. So… there’s that too. Use it until it hurts I guess. Others have found out how painful something like cascade can be if not done correctly:

> **[V21.03: After pagination+cascade change, queries are too slow to finish](https://discuss.dgraph.io/t/v21-03-after-pagination-cascade-change-queries-are-too-slow-to-finish/14184)**
>
> What I want to do Filter a large dataset, with pagination and @cascade on v21.03 What I did I could not, its too slow. Dgraph metadata ▶ dgraph version I have a query pattern for my application to use dgraph that requires using @cascade to...

---

_[View the full topic](https://discuss.dgraph.io/t/inability-to-do-simple-graphql-query-filtering-on-node-edges-like-other-graphql-baases-offer/13417)._