#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
--------------------------------+-------------------------------------------
Changes (by mtredinnick):
* owner: adrian => mtredinnick
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* needs_tests: 1 => 0
* stage: Design decision needed => Accepted
Comment:
Constructing more intelligent join types is one of the goals of the
!QuerySet refactoring -- in fact it was one of the things that started us
thinking about it. Since {{{Q()}}} objects are really just a way of
passing information to the !QuerySet construction -- and they aren't going
away -- this will be fixed as part of that. I'm reluctant to be tweaking
{{{Q()}}} objects much, since the refactoring is being worked on at the
moment (although it will be post-0.96).
Removing the patch keywords, because I don't want to apply this patch
(although thanks for writing it up anyway -- it looks reasonable). Let's
leave {{{Q()}}} objects stable in the brief runup to 0.96 and make the big
changes immediately afterwards.
--
Ticket URL: <http://code.djangoproject.com/ticket/3592#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
