#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
-------------------------------------+-------------------------------------

Comment (by Sven R. Kunze):

 Thanks, Tim. You are right, that {{{OUTER LEFT JOIN}}} is required here.

 However, I might state again that our real problem is the performance
 issue. I simultaneously posted a question on the PostgreSQL mailing list:

 https://www.postgresql.org/message-id/flat/97dbd6f9-a289-94d1-325f-
 997df87c672a%40mail.de#97dbd6f9-a289-94d1-325f-997df87c6...@mail.de

--
Ticket URL: <https://code.djangoproject.com/ticket/27260#comment:5>
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.37c738f8e2ef2133e7cd8419a03d1f48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to