I wish zope.transaction or something that replaced it would return a
Session subclass that replaces .commit and .rollback with calls to
transaction.commit and transaction.abort rather than raising an
exception with one and silently doing the wrong thing with the other :-/
Chris
On 26/06/2013
Ok, that was my fault.
I was calling rollback() on a sqla.orm.session, instead of calling
transaction.abort()
Although the documentation only forbids calling commit, it does not say
anything about rolling back an individual session :(
Thanks!
Pau.
2013/6/25 Michael Bayer
> looks like a zope.t
looks like a zope.transaction issue to me, or at least one where they'd have to
show me how they need to use the Session. They seem to be calling upon
session.transaction.prepare() directly at a time when that session.transaction
is no longer associated with the parent session. You'd need to
Hi!
I think I've stepped on the same or similar bug.
I have a software which uses zodb transactions to synchronize operations in
two databases. In the end, the two databases are the same (we are using the
exact same postgresql connection url for both). The software runs fine if
only one instance
you'd have to illustrate a working example of the code that causes that.
On Feb 20, 2013, at 6:18 AM, Christian Démolis
wrote:
> Hi,
>
> AttributeError: 'NoneType' object has no attribute 'twophase'
>
> 243.
> 244.
> 245.
> 246.
> 247.
> 248.
>
> 249.
> 250.
> 251.
> 252.
>
Hi,
AttributeError: 'NoneType' object has no attribute 'twophase'
243.
244.
245.
246.
247.
248.
249.
250.
251.
252.
"Session already has a Connection associated for the "
"given Connection's Engine")
else:
conn = bind.
