> yeah but, you should really put sanity checks in regardless....if 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 machinery so far: one in Mapper._instance() inside the "if identitykey in session.identity_map" two in EagerLoader._create_row_decorator(): one for the "can't make alias" case, and one for the "no identity key" case one in EagerLoader._create_row_processor(): for the "degrading to lazy" case (really this is the same check as one of the previous two) The EagerLoader checks I'm running full-time, the Mapper check is behind a check for a global set by the test setup. So far no hits. I think it knows I'm watching :0 On Jan 17, 2008 10:54 AM, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > 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 more frequently on a fresh build of sample data for the test > > runs. The sample data build takes 45mins, so it's painful to run > > repeatedly. I'll see if I can wire up something that will loop on it > > overnight. > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
