Re: [Twisted-Python] [sqlalchemy] Re: SQLAlchemy, Twisted, and sAsync

2010-03-26 Thread Chris Withers
King Simon-NFHD78 wrote: > The solution to this is either to eager-load all the attributes you > think you are going to need before handing the instance off to another > thread (difficult), or (probably better) to detach (expunge) the > instance from thread A's session. Are there any recommended c

Re: [Twisted-Python] [sqlalchemy] Re: SQLAlchemy, Twisted, and sAsync

2010-03-26 Thread Matthew Williams
Thank you, Simon, for clarifying this and pointing out that part of the SQLAlchemy docs... somehow I missed that part :-). On Mar 26, 2010, at 7:30 AM, King Simon-NFHD78 wrote: > I think that point should be clarified, so that people don't later > come > across this post and just accept it wi

Re: [Twisted-Python] [sqlalchemy] Re: SQLAlchemy, Twisted, and sAsync

2010-03-26 Thread Chris Withers
Matthew Williams wrote: > > "It's much trickier if you want to use the ORM, unless you are very > careful to fully eager load every thing in any possible database > operation if you have need of the information subsequently in your > twisted code. Otherwise you may block unexpectedly simply when >