Best conventions for storage of common object-type data across types

[abhijit-kar (Abhijit Kar ツ)]

I see the problem now.

You have no choice but to use id.
So if your following issue is solved, then you won’t have any problem.

@gorillastanley

But is it possible in a mutation, to make it so dgraph will update (if it exists, else create) the status object in the Job type, without having to use UID or any ID specifier?

It is annoying to get a UID before updating it in GraphQL, but in DQL you can use Upserts and fetch UID into vars and then subsequently use it in a set block in a single call.

Checkout: Running DQL in GraphQL with Upserts.

P.S. Sorry can’t provide a working example.