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

Issues Dgraph Cloud / Slash GraphQL
7

Thanks @amaster507. Actually I’m comparing Slash with other (SQL-based) GraphQL API backend as a service competitors that have this super easy node/edge relationship querying, filtering, sorting, mutations, subscriptions out of the box. In fact, it is the core beauty of GraphQL and what has drawn me to it.

Which is why it’s doubly perplexing to me that a GraphQL API services hooked up to graph db is seemingly so far behind the curve vs competitor GraphQL APIs based on SQL-based databases (MySQl, Postgres…). Again, it makes me wonder the benefit of a graph db vs simply going the route of a tried and true SQL db + GraphQL.

For example, one of those queries in the original post was taken from one of those SQL-based GraphQL API competitors:

query CorrectDataQuery {
  NodeXList(filter: {nodey: {every: {id: {equals: "456"}}}}) {
    items {
      id
      name
    }
  }
}

And you could, of course, add multiple and/or filters, sorts for nested nodes & edges beyond just that NodeY one.