I’m looking at some code that implements the following use case:
- A CBLQuery is executed with the synchronous API run() to populate an UITableView.
- User can then tap in the table rows and a new detail view opens.
- That new detail view fetches more detailed data for each of the rows plus calls and additional Live queries for a list of items related.
The problem is that the initial CBLQuery keeps running even after the user opens the detail view and the live queries results do not start coming back until the CBLQuery in the parent view is done. For the user it looks like if there is no additional detail data.
So the question is. Is there a way to stop the synchorunous CBLQuery.run? Should this be implemented with a LiveQuery which has a stop API?