Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-29 Thread Litnimax
> You can have your doubts if you like. I don't think they're correct. > Indeed "when it is ready" is the very definition of "reasonable time". Nice reply :-) > > > How can we now solve the task of "how to find rows in a table that > > have no counterpart in another table" ? > > This is already

Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-29 Thread Malcolm Tredinnick
On Thu, 2007-11-29 at 06:34 -0800, Litnimax wrote: > Hello Malcolm. > What is your estimation on merging your queryset-refactor branch? When it is ready. I"m putting as much time into it as I have spare (and then some), although I have to keep stopping to work on higher priority tickets, so it's

Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-29 Thread Litnimax
Hello Malcolm. What is your estimation on merging your queryset-refactor branch? Now INNER JOIN isnull lookup parameter does not work for related models because INNER JOIN produce cartesian product between the specified tables (that is, each and every row in the first table is joined to each and

Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-28 Thread Malcolm Tredinnick
On Wed, 2007-11-28 at 13:04 -0800, David Cramer wrote: > 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 think you'll be safe. The only difference is that certain rows won't appear when the right-hand side

Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-28 Thread David Cramer
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

Re: ManyToManyFields and LEFT OUTER JOIN

2007-11-28 Thread Malcolm Tredinnick
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

ManyToManyFields and LEFT OUTER JOIN

2007-11-28 Thread David Cramer
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