#2922: [patch] defining outer joins
----------------------------+-----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: reopened | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 1 | Needs_better_patch: 1
----------------------------+-----------------------------------------------
Comment (by mtredinnick):
Prior to 1.0, I plan on finish the refactoring of QuerySet so that the
query itself is pulled out into a separate class (it will be an attribute
inside QuerySet). This new Query class will contain attributes for the
select fields, the tables to select (and their join types and aliases), as
well as where clauses, having, group by, etc (the latter two not being
used by Django, but available for developers who might want to use them).
This object will be available after you have created the QuerySet and
before it gets turned into SQL to query the database. At that point you
can poke in any extra tables you want to join against and so. You could
even create a subclass of QuerySet that used an extended version of this
class to make such modifications easier.
So, a bunch of these "tweaking SQL" problems should become easier shortly.
It should be a transparent change for people who don't want to use the
extra stuff, but may destabilise things briefly, so I'm waiting for the
post-0.96 period before landing any code.
--
Ticket URL: <http://code.djangoproject.com/ticket/2922#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
-~----------~----~----~----~------~----~------~--~---
