2/ Transactions are not distributed across database connections http://api.rubyonrails.org/classes/ActiveRecord/Transactions/ClassMethods.html … FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!
-
-
Replying to @MorlockP
3/ So that explains why this passed the tests on my devel box but fails in production, with long-lived servers and multiple child processes.
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @BrowningMachine
@BrowningMachine@random_eddie I don't know what a "transaction coordination" is. I can imagine. But in my world a lot of the art is >1 reply 0 retweets 0 likes -
Replying to @MorlockP
@BrowningMachine@random_eddie figuring out the internal model that the tools are using, and work within that paradigm. Which I did.1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @BrowningMachine
@BrowningMachine 1 machine: transaction start create new user update new user transaction end >>1 reply 0 retweets 0 likes -
Replying to @MorlockP
@BrowningMachine 2 machines = no locking: A: create new user #1 B: create new user #2 A: update new user #2 B: update new user #21 reply 0 retweets 0 likes
@BrowningMachine that's not literally what happened but it's close enough to illustrate the problem: there is no coordination between A, B
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.