[Twisted-Python] run queries in deffered, but not in transaction
markv at lumierevfx.com
Tue Sep 15 11:19:07 EDT 2009
exarkun at twistedmatrix.com wrote:
> On 10:37 am, petshmidt at googlemail.com wrote:
>> I'd like to run several queries in background, some of them may fail.
> If you have a function along the lines of this one:
> def someInteractions(db):
> interactions = [
> Then a failure in one shouldn't affect two or three; likewise for any
> other failure or combination of failures. They are naturally (ugh, not
> a good word, but I can't think of a better one) independent. You have
> to go out of your way to associate them somehow.
I think he might mean he wants them to run sequentially, even if one fails.
You can do that explicitly via @inlineCallbacks like this:
Or with callback/errbacks, like this:
d = db.runInteraction(one).addBoth(db.runInteraction,
addBoth is a convenience method that adds the same function as a
callback and an errback:
Mark Visser, Software Director
Email: markv at lumierevfx.com
Phone: +1-514-316-1080 x3030
More information about the Twisted-Python