Transactions in GraphQL

[arijit (Arijit Das)]

@michaelcompton

How about remove @atomic and just make it @transaction with no args means I want all of these mutations in one transaction and please commit it at the end (or roll back).

Yes. This makes more sense. Updated it.

@michaelcompton

When I open a transaction how doe the TS come back? In extensions?

Yes. A transaction will have unique StartsTs and it will be returned in extensions and all succeeding requests should use that value.

@michaelcompton

Also wonder if the @transaction opens up the possiblity for case 1 to have an argument like @transaction(..., retry: true) and make retrying or not dependent on the args

I was thinking of retrying transactions if we don’t support transactions in the GraphQL query. But if we expose transaction, then the user can add the retry logic at his end. Because add retry, in that case, would unnecessarily complicate the code.