To follow up on this, would LOCK RECORD be necessary? If I didn't want to incur the lock overhead, is there a way to set the concurrency strategy on the transaction (i.e. normally use "version", but select "automerge" for this operation)?
On Saturday, November 11, 2017 at 6:53:27 PM UTC-6, Eric24 wrote: > > If two clients perform an UPDATE ADD on the same record at the same time, > do both ADD operations always succeed without an exception (since they > can't conflict with each other by definition)? What about two PUT > operations, with different/non-conflicting keys? > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
