On Sunday 13 July 2008 08:14:47 Kyle Schaffrick wrote: > On Sat, 12 Jul 2008 22:01:50 +0300 > > [EMAIL PROTECTED] wrote: > > > after the Query is long gone? > > if it is really gone/done, who should eager-load? > > I assume that it would be possible to do it after the Query is > gone, at least in theory, since lazy-loaded attributes are able to > trigger eager-loads on attributes of their instances, even after > the Query is gone. So in essence I am trying to figure out if it's > possible to add the eagerload to an instance after-the-fact. i'm trying to understand what exactly u want... do u want (for an a.b.c.d chain) to query on a (with b being lazy), then _later_ tell b.c.d to be eagerloaded and then lazyload b? i.e. some sort of options-of-relation-loading like those of-query-loading? taking a relation closer to a query in a way? like a temporary/dynamic version of current mapper/relation-options of sorts.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
