#27260: Performance Issue because of LEFT OUTER JOIN instead the better INNER 
JOIN
-------------------------------------+-------------------------------------
     Reporter:  Sven R. Kunze        |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  1.8
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I think [https://gist.github.com/akaariai/a4c1acbfedac0f2cbf3e Ansii's
 write up on join promotion] explains why `LEFT OUTER JOIN` is required
 here.

--
Ticket URL: <https://code.djangoproject.com/ticket/27260#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.230ccfb3ac28660f0a25848ea21c62d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to