#7231: New "join" parameter for the "extra" QuerySet method
-------------------------------------+-------------------------------------
Reporter: Davide | Owner: nobody
"Design" Muzzarelli | Status: closed
Type: | Component: Database layer
Uncategorized | (models, ORM)
Milestone: | Severity: Normal
Version: SVN | Keywords: queryset extra left
Resolution: wontfix | join
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 1
Needs documentation: 1 | Easy pickings: 0
Patch needs improvement: 1 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by mrmachine):
* ui_ux: => 0
* type: => Uncategorized
* severity: => Normal
* easy: => 0
Comment:
I can't reply to the discussion linked on Google Groups anymore, but
wanted to add my comment that I have found many uses for `.extra()` and
also hit the limitation of being unable to add left outer joins to a query
generated by the ORM. I would not like to see it disappear in favour of
raw SQL.
My current use case is for joining reverse generic relations on queries
against a model that does not have a `GenericRelation` field back to the
generic model (because I don't know which models it will be used with -- I
can't add models to 3rd party code).
To require the whole query in raw SQL in order to join generic relations
would mitigate the pluggability of the generic model in question.
--
Ticket URL: <https://code.djangoproject.com/ticket/7231#comment:18>
Django <https://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.
