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
This logic should be refactored in a way that it calls the implies-logic in PredicateWithValuesAndRanges instead of replicating that logic here. The only reason why that is not done right now is that this logic here indirectly excludes match mappings that involve index sargables (note that the parameter alias for created mappings is always empty). The fundamental problem for index sargables here is to synthesize the comparison range the scan should use. In fact, the predicate mapping that PredicateWithValueAndRanges.impliesCandidateRange() currently produces, refuses to return a proper comparison range (which should be coalesced from the query-originating ranges but that's not done as of now which is a bug).
The text was updated successfully, but these errors were encountered:
This logic should be refactored in a way that it calls the implies-logic in PredicateWithValuesAndRanges instead of replicating that logic here. The only reason why that is not done right now is that this logic here indirectly excludes match mappings that involve index sargables (note that the parameter alias for created mappings is always empty). The fundamental problem for index sargables here is to synthesize the comparison range the scan should use. In fact, the predicate mapping that PredicateWithValueAndRanges.impliesCandidateRange() currently produces, refuses to return a proper comparison range (which should be coalesced from the query-originating ranges but that's not done as of now which is a bug).
The text was updated successfully, but these errors were encountered: