Incorrect query results from queries in new API with multiple predicates on the same path using |
When multiple predicates use the same path and are joined using |, the optimization incorrectly treats then as if using AND rather than OR, and optimizes to false. This results in incorrect query results.
For example,
'(each.name = ''Eve'') | (each.name = ''Brian'')' incorrectly optimizes to false.
Workaround
Write this query as two separate queries and join the results.
Last updated: 9/19/14