| 1 | | Ah, I see — so even though my implementation with eagerly resolving order_by() aliases could technically work (since it was operating on a cloned query), it’s not ideal because it also affects other ORM components that rely on clear_ordering() being called in specific contexts. |
| 2 | | That makes sense — since the underlying issue is within get_aggregation(), moving the logic there should be straightforward. Thanks for clarifying! |
| | 1 | Ah, I see - so even though my implementation with eagerly resolving order_by() aliases could technically work (since it was operating on a cloned query), it’s not ideal because it also affects other ORM components that rely on clear_ordering() being called in specific contexts. |
| | 2 | That makes sense - since the underlying issue is within get_aggregation(), moving the logic there should be straightforward. Thanks for clarifying! |