Once this fix has landed, I see even ways to improve time based queries if they are not using the cornercase "complete TimeRange", but we shouldn't take the second step before the first one...
Once this fix has landed, I see even ways to improve time based queries if they are not using the cornercase "complete TimeRange", but we shouldn't take the second step before the first one...