#101516

Hi, im trying to understand the use case behind the design of the smart query builder. I know it boils down to my code, but I would like to know what is the conceptional use case. Generally, a query builder groups items by an operator. For example, I might have an entire query using the AND operator, and then groups of items within the query using the OR operator (e.g. Condition = 1 AND 2 AND (3 OR 4 OR 5)). The smart query builder allows setting the operator on a line by line basis, and then allows grouping conditions beneath an AND or OR operator. My question is, if I can throw a mix of ANDs and ORs in a single query, then why add more groups. Furthermore, if I can mix them, then what is the conceptual logic
For example, lets say I have a query such as the below, and my code isn’t evaluating with a specific Operator precedence. Is the last AND tied to the previous line, or to the first AND?
Product = A
AND
Product = B
OR
Product = C
OR
Product = D
AND
Product = E
When comparing the two below queries. Both are the same, except, one mixed all of them into one group. What would essentially be the difference between the two?

https://imgur.com/wlggqqR