Hey,
Using the idea I mentioned before, I submitted a patch.
http://code.djangoproject.com/ticket/3592
However, as you can see in my fourth comment, this isn't the necessary
usage. In fact, the "correct" implementation of an OR would use union,
like this:
SELECT * FROM package_x
INNER
On 2/27/07, Mike Axiak <[EMAIL PROTECTED]> wrote:
>
> Anyway, I'm about to overload the Q object. In this new object, Q' (i
> still haven't got a good name for it), will look up the tree (or down)
> for any ORs, and switch the join type from 'INNER JOIN' to 'OUTER
> JOIN'.
> I may have to
Hello,
Recently I've been working extensively with Q objects (that is, I've
been doing some cool things to have a user automatically create a new
set with arbitrary set combinations). Anyway, a lot of the
combinations will not work without some hackery. The reason? Q Objects
will (intelligently)
