Struggled at making upsert with assignment via the dgo client

sirkon · March 14, 2020, 1:01am

Hi.

How can I do mutation like this below with dgo client?

  upsert {
    query {
      v as var(func: eq(xid, "6459f458-8938-463a-b9b9-9c044a1d2e61")) {
        LINK as ~link
      }
    }
        
    mutation {
      delete {
        uid(LINK) <link> uid(v) .
        uid(v) * * .
      }
    }
  }

MichelDiz · March 14, 2020, 3:45am

You can get examples from the test file

github.com

dgraph-io/dgo/blob/master/upsert_test.go

/*
 * Copyright (C) 2019 Dgraph Labs, Inc. and Contributors
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package dgo_test

import (
	"context"

This file has been truncated. show original

sirkon · March 14, 2020, 8:55am

Thank you, this works. Still, I see lots of these kind of question at your discussions list. And this is rather your fault.

MichelDiz · March 14, 2020, 4:21pm

Sorry? If you have any constructive suggestions. Please do.

sirkon · March 15, 2020, 2:24am

We decided not to use Dgraph, still I have some points, hope they will help you:

The documentation is mostly about usual things pretty much every DB does: filtering, aggregation, etc. I think I would choose another established DB if I only needed these.
I would consider Dgraph only if I needed graph operations: add a node, connect two nodes, delete a node with all incoming and outgoing connections, disconnect two nodes, traversals, shortest paths. The documentation on these is pretty poor. Especially about node removal.
It is not clear how to translate queries into client requests.

PS Your query language of choice is truly special. In a bad sense. I could leave with it though.

MichelDiz · March 15, 2020, 3:08am

Thank you, I gonna take your comments into consideration. I agreed with some of them, above. That’s a thing we are working on. We indeed need to revamp the documentation and we have some internal track for this.

Cheers.