Re: Bug when OR'ing an empty Q() with a non-empty Q()?

On 6 jan, 04:14, Karen Tracey wrote: > > Near as I can tell the doc doesn't say anything about what effect an empty > Q() is supposed to have, so I don't know if the behavior you describe is a > bug or not. > > However, the behavior you describe makes sense to me if you take

Re: Bug when OR'ing an empty Q() with a non-empty Q()?

On Mon, Jan 3, 2011 at 6:16 PM, Margie Roginski wrote: > I find that if I filter by ORing an empty Q() with a non-empty Q() > that I don't get the expected result. I would expect that this should > return all objects of the specified model that the empty Q() would >

Bug when OR'ing an empty Q() with a non-empty Q()?

I find that if I filter by ORing an empty Q() with a non-empty Q() that I don't get the expected result. I would expect that this should return all objects of the specified model that the empty Q() would return. Let me use an example to be more clear: I have a single Task object with its name