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
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
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
>
On 10:25 am, albert.bra...@weiermayer.com wrote:
>On Thu, Mar 25, 2010 at 09:22:03AM +1100, Andrew Bennetts wrote:
>>
>>No; I think once loseConnection has been called dataReceived won't be
>>called again, so there's no point checking for brokenPeer in
>>dataReceived.
>
>There is a unittest that as
On Mar 26, 2010, at 3:20 AM, Chris Withers wrote:
> Matthew Williams wrote:
>> From previous posts to this and other lists, it seems that ORMs
>> and threads don't get along too well...
>
> What makes you think that?
First of all, most of my impressions about ORMs come from SQLAlchemy.
Thi
On Thu, Mar 25, 2010 at 09:22:03AM +1100, Andrew Bennetts wrote:
>
> No; I think once loseConnection has been called dataReceived won't be
> called again, so there's no point checking for brokenPeer in
> dataReceived.
There is a unittest that assumes that dataReceives still works after
sending in
Matthew Williams wrote:
> From previous posts to this and other lists, it seems that ORMs and
> threads don't get along too well...
What makes you think that?
> and, as far as I can tell, there's
> no way to get away from threads if you don't want longish queries to
> block your entire app
