> > really looking forward to the day you don't need to support oracle 8 > anymore.... >
Certainly you realize I feel *exactly* the same!!! ;) > Normally I leave the eagerload stuff to query time as query options. So > there's not much challenge there, just use a function that returns > subqueryload() instead of joinedload() based on the engine (are you using FOR > UPDATE in so many places ? doesn't all that locking kill your app in any > case ?). > Actually using FOR UPDATE in only very limited places (but it is failing even there because of an outerjoin)... > The other would be to traverse all the relationships using > mapper.iterate_properties(), find all the "lazy" flags and generate > subqueryload() options for them. That is straightforward but would require > the thinking cap/read-the-source-cap to get all the way through it. I suppose this is the route I need because I really want a few relationships to be able to be marked as lazy=False. I notice that specifying subqueryload() for a relationship marked as lazy=False is smart enough to *remove* the joinedload from the first query... very nice! Thanks for your help again. -- 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.
