> So this is some variant of, "i have a bunch of objects and I'd like to ... <snip lots of reasons why this should not be a standard feature>
Yeah, I understand what I'm asking for here, and I would never expect this kind of optimization to kick in by default. Instead, it would only be used in those cases where profiling has shown that there is a bottleneck. I have profiled my code to find out where the bottlenecks are, so I think I fall into the category of individuals who actually know how to use a feature like this. > I think Hibernate might have this kind of loading available... I wouldn't be surprised. From my use of Hibernate (which was quite a while ago now) my inclination was that it had lots of options for complex and highly customized optimizations, like the one I'm trying to do. > You'd start using plain session.query() to get the rows you want, hash > together the collections as desired, and then apply them to the > already loaded objects using the attributes.set_committed_value() > function which is used for this purpose (pseudocode follows)....(also > use trunk rev 6066 since I had to fix set_committed_value()): I suppose r6066 is a 0.5 revision number? How well does set_committed_value() work in SA 0.4.7 ? I haven't upgraded to SA 0.5 yet, and I'd rather not do that right now if I can avoid it. However, if this can't be done with 0.4... Thanks a lot for the tips on how to approach this problem. That's exactly what I needed. ~ Daniel --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---