Found on branch releases/v20.11 commit hash: e1ee8595ec0d6d8e91a9292a4eb28738f1fbdd6c schema type Foo { id: String! @id bar: Bar! @hasInverse(field: foo) } type Bar { id: String! @id foo: Foo! } mutation mutation { addFoo(input: [ { id: "1231" bar: { id: "12344…

This has been fixed in master with the merging of PR . The fix simply ignores any inverse field (same or any other parent) provided with the mutation.

[Bug] Not sure how to name this bug - please help out

Issues GraphQL

maaft February 20, 2021, 6:56pm 3

Yes, I know that this is not necessary. Just stumbled across this by mistake.

I guess solution 2 would be fitting. Thanks!

Topic		Replies	Views
Best way to avoid "duplicate XID found" GraphQL kind:enhancement , status:accepted , ticket:created	9	1971	October 22, 2020
How to perform add mutation when multiple different fields reference the same node. (Duplicate XID found) Dgraph kind:question	0	452	April 4, 2022
Add id manually while using GraphQL GraphQL mutation , graphql , status:accepted , kind:bug , ticket:created	19	3402	September 8, 2020
Multiple ID issue GraphQL status:accepted , ticket:created	1	1021	April 5, 2021
GraphQL equivalient to Insert on Duplicate Key Update GraphQL kind:feature , area:mutations	1	1671	August 11, 2020

[Bug] Not sure how to name this bug - please help out

Related topics