On Sep 4, 2007, at 2:56 AM, Arun Kumar PG wrote:
> Guys, > > Was wondering if we have 10 tables or so which are related to each > other and are required during let's say report generation then if > I specify eagerloading for all those attributes which are related > to these tables then down the line as the records in the table > grows the temp tables generated in the join (left outer in > eagerloading) will be massive before appying the where clause. So I > guess we should worry about this or is that fine as long as the > tables are getting join on primary/foreign key as the query plan > looks decent ? > > I am doing this for 7-8 tables out of which data is growing > continuously in couple tables with a factor of 2XN every month. I > am worried if eagerloading may be a problem in the sense if it will > bring the db server down to knees some day considering the joins > happening ? FYI: the eager loading is specified at the Query level > so that I can optimize where I really need. > > But currently it's faster as compared to executing individual > query. And in my case if I go with individual queries due to lazy > load it takes forever. And in many cases the request times out when > using a web browser. So eargerloading is better but just worried > about speed. Any good guidelines on how we should use eagerloading, > best practises, any limitation etc ? > you might want to look into creating views for each thing that you need to select, thus moving the complexity of fine tuning the joins over to the database side. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
