#3592: Allowing Q Objects to select between OUTER and INNER joins (semi-
intelligently)
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: Q,QuerySet,JOINs | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------+-------------------------------------------
Comment (by [EMAIL PROTECTED]):
I would love to use UNION. It is the right way to do it (it is logically
what is meant by |). However, it seems I cannot do that without doing
enough of a rewrite as to really merit a refactoring of QuerySet. This is
meant to buy the current Q's some time...
What type data are you working with? I'm assuming you have indices for the
columns you're joining on. If so, how many rows do you have that it's a
problem?
Just curious--maybe there's a way to optimize this further?
--
Ticket URL: <http://code.djangoproject.com/ticket/3592#comment:11>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
