On 19 July 2016 at 23:22, Mike Bayer <mike...@zzzcomputing.com> wrote:
> > > On 07/19/2016 05:20 PM, Martijn van Oosterhout wrote: > >> >> >> Thanks. On the way home though I had a thought: wouldn't it be simpler >> to run the original query with yield_from(), and then after each block >> run the query with a filter on the primary keys returned, and add all >> the joinedload/subqueryload/etc options to this query, run it and rely >> on the identity map to fix it for the objects returned the first time. >> Or is that something we cannot rely on? >> > > it works for the loading you're doing, where the primary keys of what's > been fetched are fed into the subsequent query. But it doesnt work for > current subquery loading which does not make use of those identifiers, nor > for joined loading which does OUTER JOIN onto the original query at once > (doing "joinedload" as a separate query is essentially what subquery > loading already is). > > Ah, good point. Pity. I like the whole generative interface for the joinedload/subqueryload/etc and would have liked to reuse that machinery somehow. Given I'm trying to eager load several levels of relationships, it'd be nice to automate that somehow... Have a nice day, -- Martijn van Oosterhout <klep...@gmail.com> http://svana.org/kleptog/ -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
