Transactions in GraphQL

[eugaia]

@michaelcompton

This will mean open a new transaction, do m1 and m2, then commit. otherwise fail all.

mutation @transaction(commit: true) {
 m1(...) {...}
 m2(...){...}
}

This will mean keep the transaction open and return the details in the extensions

mutation @transaction {
 m1(...) {...}
 m2(...){...}
}

What about changing it to:

This will mean open a new transaction, do m1 and m2, then commit, otherwise fail all.

mutation @transaction {
 m1(...) {...}
 m2(...) {...}
}

This will mean keep the transaction open and return the details in the extensions.

mutation @transaction(commit: false) {
 m1(...) {...}
 m2(...) {...}
}

In determining which of these two is a better option, I think the key question here is whether most users are more likely to want to commit the transaction in a single request, or if in general they’re more likely to want to return the transaction to do some more client-side work before committing. Also, what would be the most natural expectation for developers?

My guess is that most would expect @transaction to commit everything (if there are no errors), unless otherwise stated, but maybe more experienced Dgraph users would feel differently.

Any update on the roadmap for this?

Thanks.