Upsert for uniqueness, how to know if the Cond blocked the Mutation?

[mko0815]

@MichelDiz

That looks normal to me. Not sure what you mean. Maybe this is related to the Go Client only? What exactly is empty? Test it in Ratel first.

this was related to your post:

@MichelDiz

@mko0815

> query {
		user as var(func: eq(email, %s))
	}
> ```

The query response will be empty cuz this query is empty. It should be like:

query {
		user as var(func: eq(email, %s)) {
                     UID
                     email
                     name
              }
	}

That way you will have responses in the query response key.

the query in the documentation is the same as mine. but you said that mine is wrong as I didn’t select any fields to return.

@MichelDiz

So you did something wrong. I’m 100% that it should ignore if the user exists.

that’s what I meant: it ignores the user if it exists:

@mko0815

but the map of UIDs is filled in case it was a new user. (so the upsert query didn’t stop the mutation)

---

@MichelDiz

What exactly is empty?

The json in the response from the request is empty:

@mko0815

json:"{}"