1/ This bug can only exist if Rails ActiveRecord SQL transactions don't work. This bug does exist. Therefore
@BrowningMachine
1 machine:
transaction start
create new user
update new user
transaction end
>>
-
-
@BrowningMachine 2 machines = no locking: A: create new user #1 B: create new user #2 A: update new user #2 B: update new user #2 -
@BrowningMachine that's not literally what happened but it's close enough to illustrate the problem: there is no coordination between A, B
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.