| 14 |  | Can't be translated to equivalentDjango ORM expression even if using `extra()` command, because there isn't anywhere a possibility to set additional arguments on `JOIN` clauses. And when I'm using  `filter(Q(argument) | ...)` it happens to always push all arguments to `WHERE` clause, which just causes a performance hit. I wish there was some parameter which would determine the destination of the argument, whether it has to go to the (last) `JOIN` clause, or to be put in `WHERE` (which goes by default). Also, I'm not able to comprehend how to perform correctly `LEFT JOIN` so in the end I have made some jumbled up expression which is completely inefficient (as it executes two queries, but it's the only way to do the same from above and get `QuerySet` in return): | 
          
            |  | 14 | Can't be translated to the **equivalent** Django ORM expression even if using `extra()` command, because there isn't anywhere a possibility to set additional arguments on `JOIN` clauses. And when I'm using  `filter(Q(argument) | ...)` it happens to always push all arguments to `WHERE` clause, which just causes a performance hit. I wish there was some parameter which would determine the destination of the argument, whether it has to go to the (last) `JOIN` clause, or to be put in `WHERE` (which goes by default). Also, I'm not able to comprehend how to perform correctly `LEFT JOIN` so in the end I have made some jumbled up expression which is completely inefficient (as it executes two queries, but it's the only way to do the same from above and get `QuerySet` in return): |