Hi Erik,
In general:
- queries with NOT are not indexed
- LIKE operator cannot be used with indexes in general
- AND operations can be indexed if you have a multi-property index, but not
on multiple indexes on the same query
- the new SQL executor in v 3.0 is much smarter at query optimization and
I'm trying to create some indexed queries and I want to make sure I
understand the documentation. What happens when an AND or OR is used with
NOT or LIKE? Does the NOT force the whole query to avoid an index? Does a
LIKE force the index to need a ranged query for everything?
--
---
You recei
