Open Stack

On 07/30/2014 09:48 AM, Doug Wiegley wrote:
>> I'd have to look at the Neutron code, but I suspect that a simple
>> strategy of issuing the UPDATE SQL statement with a WHERE condition that
>
> I¹m assuming the locking is for serializing code, whereas for what you
> describe above, is there some reason we wouldn¹t just use a transaction?

Because you can't do a transaction from two different threads...

The compare and update strategy is for avoiding the use of SELECT FOR 
UPDATE.

Best,
-jay