Context Navigation

Changes between Initial Version and Version 1 of Ticket #16554, comment 2

initial	v1
1	1	I would argue that this is still a bug and should be left open. There is no conceivable situation in which you would need both joins. An extra join can severely impact the performance of a query, especially when dealing with large datasets. The ORM should recognize these situations and optimize as needed by removing the unnecessary joins.
2	2
3		Sure, you can avoid the extra join in the multiple .filter() example, but there are some situations in which ~~the extra join~~ cannot be avoided, as illustrated above with the aggregate query.
	3	Sure, you can avoid the extra join in the multiple .filter() example, but there are some situations in which it cannot be avoided, as illustrated above with the aggregate query.