Changes between Initial Version and Version 1 of Ticket #27260, comment 5


Ignore:
Timestamp:
Sep 23, 2016, 1:36:09 AM (8 years ago)
Author:
Sven R. Kunze

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27260, comment 5

    initial v1  
    11Thanks, Tim. You are right, that {{{OUTER LEFT JOIN}}} is required here.
    22
    3 However, I might state again that our real problem is the performance issue. I simultaneously posted a question on the PostgreSQL mailing list:
     3However, I might state again that our real problem is the performance issue. As we don't know who's responsible in the end, I simultaneously posted a question on the PostgreSQL mailing list:
    44
    5 https://www.postgresql.org/message-id/flat/97dbd6f9-a289-94d1-325f-997df87c672a%40mail.de#97dbd6f9-a289-94d1-325f-997df87c672a@mail.de
     5https://www.postgresql.org/message-id/flat/97dbd6f9-a289-94d1-325f-997df87c672a%40mail.de
     6
     7
     8So, it seems as if Django could also solve it by using UNION or generating subquery plans.
Back to Top