Just discovered what appears to be a pretty bad bug:
On the ohiomollusk server running v7.10.2.2, a query that uses OR operators on the taxon table query results has broken since the update pushed a few days ago. After some testing, I’ve found that it is actually all OR queries following certain conditions are broken by the update to 7.10.2.2.
The issue is not limited to the taxon tree, I can replicate the issue in the geography tree. Issue seems to be limited to OR queries on tree fields, normal table queries work correctly as far as I can tell. I believe all OR queries that DON’T use an OR between one normal condition and one negated condition are broken?
If you use the NOT operator, you can still use OR, but it looks like it’s only for queries with one NOT. If you use two normal conditions that aren’t negated, the logic of the results is incorrect. Don’t have time to document more thoroughly, but see screenshots below.
OR with two normal conditions (doesn’t work, incorrect result)
We have confirmed through internal testing that this does indicate a regression with the query builder OR operator.
We have concisely determined the issue to stem from queries with a mapped field using the OR function, where more than value is true / not negated.
This has been added to GitHub and linked with this post for developers to address. Feel free to review this and add any details or comments as necessary:
