You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
The current pattern when chaining filters do not merge queries together:
manager.filter(query1).exclude(query2)
When evaluating the queryset, it will loop over available values, return the one that match query1, then loop other these remaining values and exclude the one that match query2.
It would be more efficient to loop only once on all values, and return only values that match all queries.
The text was updated successfully, but these errors were encountered:
Thanks for the link, I never heard about it but there are sure interesting ideas in there.
Regarding this specific issue, though, this is something I'm working on by compiling queries together, before running them against the dataset. You can see the feature/backend branch for more details.
Cool. I thought it could be something to be done using sets' intersection. I will follow along on the branch. Maybe add the reference link to the solution you are trying then.
The current pattern when chaining filters do not merge queries together:
When evaluating the queryset, it will loop over available values, return the one that match query1, then loop other these remaining values and exclude the one that match query2.
It would be more efficient to loop only once on all values, and return only values that match all queries.
The text was updated successfully, but these errors were encountered: