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 fails. Looks like it may be becoming a bad idea to rely on eager fetches.... On Jan 14, 2008 10:06 PM, Rick Morrison <[EMAIL PROTECTED]> wrote: > 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 might give a clue. Whenever an eagerly > loaded item is missing in the list of results, so are all the values that > follow. For example, if I shorten my original list to fifty items, 0-43 > might be ok. After item 43, then *every* remaining item is missing, so I > would think that it's something that traverses the list of results and once > it breaks, it stops the traverse. > > as far as I know, none of the otherwise eagerly loaded items are already > mapped, and the joins are not self-referential. It's a three-way join of > three different tables as outlined in the orig post. So it might be > something new. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
