Add id manually while using GraphQL

[amaster507 (Anthony Master)]

@MichelDiz

If you wanna bulk data into Dgraph, you should do it via Liveload. Not GraphQL mutation.

Bahumbug, lol. And this is where we differ. I want to keep the logical restrictions imposed by the graphql endpoint that the liveloader does not honor. We are not talking about importing GBs of data, but rather a users Contact lists from an excel sheet of ~100 contacts, which could contain (as we would have to parse in a script) a link to contacts family, and employer, and friends. These would all be imported at once, and hopefully by a mutation in graphql

As we start to integrate with other graphDB services I am sure we will start to get data going both ways in JSON format and we would want to make the mutations again with graphql.

Anyways, I think this is stepping away from the OP, but just my feedback.

@MichelDiz

@spinelsun

Michal doesn’t have the revers connection with Or.

Can you please explain why?

I think that the reason is that “Or” is a parent, and your query asks for Childs. So “Or” isn’t a Child of “Michal”. The inverse doesn’t mean that it will appear for you anyway, you need a way to query inverse. In DQL we use the “tilde” notation. That means, <~friend> will return the inverse ones. You can’t mix the inverse and the real direction on a query result. It could potentially break applications and confuses the user.

@amaster507

It looks like you found a bug:

nah, feels like a misunderstanding tho. See the comment above.

@amaster507

I think we have a bug here where the person “Or” is only linked to Michal with a one-way link instead of a two way as it should have been done.

BTW, do we have a <~friend> notation in GraphQL? I think that the inverse one is used for other proposes. Not to show inversed edges, just to use them. I can be wrong tho.

Is my understanding here correct:

@hasInverse GraphQL to DQL mapping

This is done purposefully. @hasInverse is not the equivalent to adding the @reverse directive in DQL. On the graphql schema, the @hasInverse directive creates logic in the resolvers to add/update/delete the inverse edge of the specified type. There is more to the underlying reasoning behind this but overall it is to allow for better type notatation predicate control. In DQL a single predicate can be applied between two types, but in GQL, if a Post Type has an author predicate and a Author Type …

if so, then it is a bug. I think @pawan agrees that it is a bug, as he added the bug tag.