| 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. |
| | 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 of the problem, as I certainly can't help to myself in solving this. I really tried hard focusing on and examining ORM features in detail but no avail. I doubt that anyone would properly solve it until some new feature is added which allows such. |