#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
----------------------------+-----------------------------------------------
Changes (by Michael Radziej <[EMAIL PROTECTED]>):
* keywords: reopen =>
* needs_better_patch: 0 => 1
* stage: Unreviewed => Design decision needed
* needs_tests: 0 => 1
* needs_docs: 0 => 1
Comment:
Jonathan, any ideas from your side according to the syntax? Though I use
the patch above, I don't really like it. And the patch itself is not very
good, it should use queryset.joins instead of introducing just another
attribute _joins.
Personally, I'd rather have a way to turn an arbitrary sql statement into
a QuerySet (provided that the statement selects all fields of model and
each result row represents one model, of course). There are lots of cases
when the ORM hits its limits.
--
Ticket URL: <http://code.djangoproject.com/ticket/2922#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
