Indeed this JSON store is transactional and takes advantage of this feature provided by badger.
But CAS is another story and is orthogonal to transactions. Even when using common RDBMSs we need some form of optimistic concurrency. Assume we are about to update the balance for an account. How to make sure that the balance remained unchanged during our app logic? Applying new changes even with transactions, will simply overwrite any changes made meanwhile. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
