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
If a user wants to run a MajorityLocation query excluding unlocatable subscribers, and also the same MajorityLocation query including unlocatable subscribers, these would be two independent queries. But the second case actually requires running the first query, and then joining this to the set of all subscribers with weighted locations. I think it would be beneficial to break down MajorityLocation a little so that a query with include_unlocatable=True uses the corresponding query with include_unlocatable=False as a sub-query, to improve cache re-use in this situation.
If a user wants to run a
MajorityLocation
query excluding unlocatable subscribers, and also the sameMajorityLocation
query including unlocatable subscribers, these would be two independent queries. But the second case actually requires running the first query, and then joining this to the set of all subscribers with weighted locations. I think it would be beneficial to break downMajorityLocation
a little so that a query withinclude_unlocatable=True
uses the corresponding query withinclude_unlocatable=False
as a sub-query, to improve cache re-use in this situation.Originally posted by @jc-harrison in #5128 (comment)
The text was updated successfully, but these errors were encountered: