How does atomic update work with multiple clients? Assuming that there is no matching record to begin with the access won’t be locked. It seems like two threads could write conflicting data since they both see no existing record (NER). Is that correct? Or is there something that will serialize the writes so that only one of them sees the NER state?
- On duplicate key update Jon Strayer
- Re: On duplicate key update Josh Elser
- Re: On duplicate key update Jon Strayer
- Re: On duplicate key update James Taylor