Okay, I guess I have fixed it. I say I guess because the solution
between my app and a simple test scenario is different. The new test
scenario is here:
https://gist.github.com/1366878
Basically the same as before, but now you can vary between using
Transaction or SQLAlchemy directly
On Nov 15, 2011, at 7:09 AM, Vlad K. wrote:
Why I didn't think of this earlier? Transaction complains if you use
session.commit() or session.begin_nested() directly, wants you to use
transaction.commit() and transaction.savepoint() instead and it just didn't
occur to me to try
It's been hard to follow what has actually been tried, but I just wanted to
point some stuff out about zope.sqlalchemy (the code for it is literally 1
small file and shouldn't be talked about with such a scary tone).
When doing transaction.savepoint() it returns a savepoint object that calls
