Anything you can think of off hand that's going to hurt by just changing it to INNER JOIN right now if we dont use the isnull support.
I'm also wondering if it may cause many rows to return (i can't remember how left joins work, as I don't use them much) vs a single row, but we use it with GROUP BY statements either way. On Nov 28, 11:50 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2007-11-28 at 11:00 -0800, David Cramer wrote: > > I was debugging a query earlier and noticed that ManyToMany filter > > calls perform a left outer join. > > > The only use case of this I could come up with is > > myfield__isnull=True. Are there any other reasons this is needed? > > > If not I'd like to propose changing this to use INNER JOIN (on the > > exception of the isnull call). > > Via the magic of time machines, this has already been done on > queryset-refactor branch. You also need it with certain "or" > combinations of queries. > > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
