| 2 | | I understand that it has a duplicate title, but only in that terms, because the problems differ - in that issue it is provided the equivalent solution using `extra()` and `aggregate()` method, while here, there isn't any possible one. It addresses the different scope of the problem described in the title, which technically (if pointed out on efficiency like always), is unsolvable using current ORM expressions. Therefore, I expect from you or other people involved in Django development to provide or guide me towards the proper solution (using any of the ORM expressions, including `extra()` of course), as I certainly can't help myself, because I really tried hard focusing on and examining ORM features in detail, and asking others - but no avail. I doubt that anyone would properly solve it until some new feature is added which would allow such thing to be achieved, so I think that this definitely deserves to be a separate issue. |
| | 2 | I understand that it had a duplicate title with the issue you've mentioned, but only in that terms, because the problems differ - in that issue it is provided the equivalent solution using `extra()` and `aggregate()` method, while here, there isn't any possible one. It addresses the different scope of the problem described in the title, which technically (if pointed out on efficiency like always), is unsolvable using current ORM expressions. Therefore, I expect from you or other people involved in Django development to provide or guide me towards the proper solution (using any of the ORM expressions, including `extra()` of course), as I certainly can't help myself, because I really tried hard focusing on and examining ORM features in detail, and asking others - but no avail. I doubt that anyone would properly solve it until some new feature is added which would allow such thing to be achieved, so I think that this definitely deserves to be a separate issue. |