(Chris's colleague here)
On Thursday, 2 April 2015 17:23:13 UTC+1, Michael Bayer wrote:
this issue is fixed for 0.9.10 and 1.0.0b5, you can test now using either
latest master or the rel_0_9 branch.
Just wanted to say thank you very much for the prompt fix; I continue to be
amazed at
On 4/2/15 10:01 AM, Chris Wilson wrote:
Dear SQLAlchemy developers,
I think I've found a problem with SQLAlchemy not rolling back changes
to instances that are committed in an inner nested transaction, when
the outer nested transaction rolls back.
The manual says:
When
Dear SQLAlchemy developers,
I think I've found a problem with SQLAlchemy not rolling back changes to
instances that are committed in an inner nested transaction, when the outer
nested transaction rolls back.
The manual says:
When begin_nested()
On 4/2/15 11:54 AM, Mike Bayer wrote:
it's a bug, and I've captured the origin, diagnosis and probable
solution here:
https://bitbucket.org/zzzeek/sqlalchemy/issue/3352/nested-begin_nested-blocks-dont-track
this issue is fixed for 0.9.10 and 1.0.0b5, you can test now using
either latest
