Under what scenarios does Dgraph return an array in place of a string?

[dpk (Ehhh)]

@MichelDiz

This looks odd. It should be like:

		mu.setSetJson({
			'bar': [{'uid': 'uid(bar2)'}], #be careful here, make sure it is ONE to ONE
			'dgraph.type': 'Foo',
		});

I haven’t (until now) tried mutating the predicate using an array in setJson. I wouldn’t have expected it to work. However, the results are the same with all four options below:

mu.setSetJson({
  bar: 'uid(bar2)',
});

mu.setSetJson({
  bar: {uid: 'uid(bar2)'},
});

mu.setSetJson({
  bar: ['uid(bar2)'],
});

mu.setSetJson({
  bar: [{uid: 'uid(bar2)'}],
});

That is, I sometimes get an array response to the query in postCommit and sometimes not.

@MichelDiz

Do you really need to pass 'dgraph.type': 'Foo' all the time? You should add it in the creation, not in an upsert. But if you are creating it during the upsert, It is fine. Just a small thing, not important.

No not in this case, it’s just habit on my part. A long while back I had forgotten it in a few places and a lot of stuff broke so now I’ve just been explicit every time.

@MichelDiz

Line 99

I’m not sure what you are doing in that line. You say “Switch to bar 3” is it a migration of nodes to other references? You should unlink the others if it is a migration.

Fix the syntax there.

I don’t know what you mean – I’m trying to replace the value in the predicate. Do I need to do a delete mutation and then a set mutation whenever I want to replace a value in a scalar/uid predicate?

@MichelDiz

Also, if you have a lot of foos foo as var(func: type(Foo)) you will link them all in that upsert. That might be there the issue.

Yeah – in this case, I have one, so I could make a (mostly) minimally reproducible demo. I’m more explicit in my real code.