Re: [pylons-discuss] Re: How to handle DB transaction failures/request race conditions

Jonathan gives a pretty good description of how the packages fit together. He left one out, however, which I'll mention. https://docs.pylonsproject.org/projects/pyramid-retry/en/latest/ pyramid_retry wraps pyramid_tm and looks for failed transactions that failed due to some

Re: [pylons-discuss] How to handle DB transaction failures/request race conditions

Hi Jens, You also might find some background information here: https://websauna.org/docs/narrative/modelling/occ.html Br, Mikko On 27 November 2017 at 11:00, wrote: > Hello, > > Looking at the SQLAlchemy cookie cutter >

[pylons-discuss] Re: How to handle DB transaction failures/request race conditions

The sqlalchemy cookie cutter uses pyramid_tm to handle the transaction. The docs on that package should answer all your questions: https://docs.pylonsproject.org/projects/pyramid_tm/en/latest/ Basically what happens is this: * the actual transaction management is provided by zope's

Re: [pylons-discuss] How to handle DB transaction failures/request race conditions

On Mon, Nov 27, 2017 at 01:00:00AM -0800, jens.troe...@gmail.com wrote: > Hello, > > Looking at the SQLAlchemy cookie cutter > , a request gets > its own transaction-backed db session, and on its way out a response > commits that

[pylons-discuss] How to handle DB transaction failures/request race conditions

Hello, Looking at the SQLAlchemy cookie cutter , a request gets its own transaction-backed db session, and on its way out a response commits that transaction and closes the session. There are activation