On Jan 16, 2008, at 8:44 PM, Rick Morrison wrote:
Thanks for the tips.
I am sure that none of the objects are loaded beforehand: I've got
it localized to a run of unit tests that I can start afresh each time.
So far it's intermittent, seems to happen only one of say 10 runs.
Happens
yeah but, you should really put sanity checks in regardlessif you
run the thing all night and you get the error 10 times, that doesnt
say much unless you can narrow it down.
uh, yeah I figured that was assumed. In addition to some application checks,
I've got four checks in the SA
I still have no answer as to what this might be, but I am starting to see it
more often.
It's now biting me a bit harder as it's beginning to happen on items that I
cache on startup and then .expunge(). When I later go to access a relation
on the expunged item, the trigger of the lazy loader
On Jan 16, 2008, at 7:32 PM, Rick Morrison wrote:
I still have no answer as to what this might be, but I am starting
to see it more often.
It's now biting me a bit harder as it's beginning to happen on items
that I cache on startup and then .expunge(). When I later go to
access a
Thanks for the tips.
I am sure that none of the objects are loaded beforehand: I've got it
localized to a run of unit tests that I can start afresh each time.
So far it's intermittent, seems to happen only one of say 10 runs. Happens
more frequently on a fresh build of sample data for the test
Update: it's not the length of the fetch, a smaller fetch still has holes
it it. Looks as if something might be short-circuiting the SA internal
join?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy
On Jan 14, 2008, at 8:11 PM, Rick Morrison wrote:
This is going to sound kind of strange, but I've noticed that
sometimes when doing fairly large eager loads, that not everything
always loads.
So running, say
custlist = S.query(Customer).options(eagerload('addresses'),
I had already put together a short test case which as usual is of course
working fine, but it's greatly simpler than the in-application use and uses
sqlite instead of MSSQL, so I'll bang on it from time to time as I've got a
few seconds and I'll see where it goes.
I did notice some behavior that
