Why does a mutation return not the nodes of the mutated node, but the nodes that have a same value as the mutated node? - GraphQL Tour Schema site 3

Why? Why doesn’t it return only alice’s data, but return all employee data? This is not the baviour I would have expected

second question: How would I have been able to answer my first question myself? I used the search but nobody asked the same. But I should have been able to answer me my first question myself somehow, why it returns all existing employees of the company, instead of only alice’s data. How could I have been able answered me that myself? Which approach, which steps, do I have to take to answer me these questions myself?

In https://dgraph.io/docs/graphql/mutations/add/ I wasn’t able to find any information about that behavior.

It is a graphql spec:



1 Like

It returns only Alice at the root level because that is what was mutated, but then it traverses to the employer and then to all the other employees. At the nested edge there is no filter to restrict to only the updated user.

1 Like