Mutation variables go away since v0.9.0

selmeci · January 24, 2018, 6:16pm

Hi everyone,

according to github, mutation variables are no longer supported since version 0.9.0.

According to release note, this functionality can now easily be achieved via transactions.
Unfortunatly, I cannot find any example how to do it.

Does anyone any example?

Thank you.

sboorlagadda · January 24, 2018, 6:45pm

Hello Selmeci,

Transaction do provide a way to do query and use the queried results to mutate with in your transaction.
Let me know if this example helps

github.com

dgraph-io/dgraph4j/blob/master/src/test/java/io/dgraph/AcctUpsertTest.java#L55


      for (int age : ages) {
        Account account = new Account();
        account.first = first;
        account.last = last;
        account.age = age;
        accounts.add(account);
      }
    }
  }

  String schema =
      ""
          + "   first:  string   @index(term) @upsert .\n"
          + "   last:   string   @index(hash) @upsert .\n"
          + "   age:    int      @index(int)  @upsert .\n"
          + "   when:   int                   .\n";
  Operation op = Operation.newBuilder().setSchema(schema).build();
  dgraphClient.alter(op);
}

private void tryUpsert(Account account) {

Sai

Topic		Replies	Views
Javascript client: Are variables supported in mutation blocks? Users	5	718	January 28, 2018
Example of using variable in mutation? Users	2	2112	October 9, 2017
Support DQL variables in mutations Dgraph dgraph , kind:enhancement , status:accepted , area:upsert , area:querylang:vars	14	2391	October 4, 2022
Query Then Mutate in Ratel Users	5	974	March 22, 2018
How to set variable in mutation during upsert? Dgraph kind:question , area:upsert	5	983	November 2, 2020

Mutation variables go away since v0.9.0

Related topics