On Monday, December 20, 2021, Sylvain Déve <sylvain.d...@protonmail.com> wrote:
> > To summarize, how can I allow for multiple updates of the same attributes, > one after another, even when these updates are requested almost at the same > time from independent, uncontrollable client requests? > Most people use an application connect pool. You replace “connect” with a call to get a connection from the pool. When you are done you release the connect back to the pool. Concurrency is then done by having a pool size greater than one. If you try doing more concurrent work than the pool size allows the pool call should block and/lr return a nothing upon which you loop and try again. David J.