Re: [sqlalchemy] Share uncommitted state between differing connections

2011-10-22 Thread Denis Krienbühl
2011/10/22 Michael Bayer : > A single object can only be linked to one Session at a time.  You can > transfer state to another while leaving the original unaffected using > Session.merge().  If the objects themselves are persistent (i.e. have an id) > and are clean (i.e have been flushed, no pe

Re: [sqlalchemy] Share uncommitted state between differing connections

2011-10-21 Thread Michael Bayer
On Oct 21, 2011, at 3:54 PM, Denis wrote: > > Is there any way for me to share the pending objects of the serialized > session with the read session? I would like to ensure that the read > session used in the same request as the serialized session sees the > same data. A single object can only

[sqlalchemy] Share uncommitted state between differing connections

2011-10-21 Thread Denis
I'm developing a Plone module with sqlalchemy 0.7.3 and postgresql 9.1. I'm making use of postgres' new 'True Serializiation' feature to ensure that concurrent writes do not lead to conflicts. Since true serialization is quite expensive I started to use two connections for each server thread: - O