Thanks for the comment. If I understand you correctly, I'm going in a similar direction in trying to keep transactions short. If there is a write to the database, I want a commit or rollback shortly thereafter (usually on the order of milliseconds rather than anywhere approaching the 5 second timeout). The point of my utility class is to try to find the places where my teammates or I have accidentally not conformed to that ideal rather than having QA report every few days that they saw an OperationalError in the logs.
If you have any further advice about your shift in strategies, I'd be happy to hear them. Thanks, Eric On Wednesday, April 1, 2015 at 9:05:55 AM UTC-6, Jonathan Vanasco wrote: > > On a sidenote, I found the best approach to a similar problem (which used > Twisted) was to make the transactions as short as possible. Three hours of > changing how transactions were used was far more helpful than 2 weeks of > trying to get around long transactions. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
