Only some of the Parse provided fields have index’s created by Parse. Most fields created by developers, like
displayUntil won’t have an index unless the developer adds it manually. It’s important to note there are pros/cons to index’s and they aren’t always needed. In addition, most of the Parse docs for performance considerations are written for mongo, so if you are using mongo they may still apply. Postgres uses should look into what makes since.
@lsmilek1 your comment mentions “cloud job” which means it’s using the JS SDK. I’m sure there are different ways to accomplish the query using the JS SDK. The original question in this post is how to do this using the Swift SDK.
Lastly, there is usually multiple ways to construct a query, if you are trying to optimize performance, you should use
explain to see what works best for you.
equatTo with a
Date will probably start to yield problems at some point as it’s hard to have an “exact” date (seconds, milliseconds, etc). It’s best to use <, <=, >, >= with a