I agree, having the ORM create O(n) table joins by default would be a bad idea, but I wonder if we could provide an option to have it do that.
On Jun 28, 7:49 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sat, 2008-06-28 at 17:29 -0700, [EMAIL PROTECTED] wrote: > > Malcolm, does select_related work with 1-to-1's (and thus would do the > > preloading)? > > No, it doesn't. You still have the O(n) table join problem, since it > needs to query every single descendent table to find the right rows. > Don't just think of a parent with two child classes. Consider the case > of grandchild and further classes, too. That isn't a path you want to go > down regularly. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
