> > On Thu, 2006-10-26 at 09:20 +0100, Robin Haswell wrote: > > > [EMAIL PROTECTED] wrote: > > > > I think we need an optimizing sql compiler for tg. All my sqlobject > > > > code is slow there is no turboboost switch. Its like my included > > > > batteries are one shots. I need jumper cables over here. > > > > > > Sorry mate, SQLObject is slow by design. > > > > *** This is of great interest to me. Can someone explain the reason for > > SO being slow? I'm using it in what will hopefully become a very > > high-traffic site, and although I'm memcached-ing and squid-ing the hell > > out of everything, this is still of great concern. > > > There's still a performance problem with Many-to-Many relationships, > the default ones populate lists which has to fetch each object and it > ends up being slow. > > Now you can optimize this by using SO* instead of plain cols as > SORelatedJoin instead of RelatedJoin,etc.
*** Thanks for the info. Is this documented anywhere? I'm specifically interested to know: 1. How exactly the SO* mechanisms work, and improve things over the vanilla equivalents. 2. What disadvantages they have over the vanilla equivalents (otherwise we'd be using them all the time, right?). 3. I've seen mention of an SQLRelatedJoin, and an SOSQLRelatedJoin. How do they fit in? Thanks again, Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
