Why are view indexes only updated incrementally on demand, after a view is queried? It seems that the best time to index documents is as soon as they are changed. That way when a view is queried all it has to do is rerun the query, not index all changed documents, which can be slow.
I know this can be done with LiveQueries, but they come with re-querying and memory costs. Basically I am looking for another *CBLIndexUpdateMode* such as *kCBLUpdateIndexContinuous*. I'm wondering if this is technically possible or what that the design decision against it was. Thanks, Martin -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/d0f9f66b-fe09-4ca3-8a43-8fdc1e3ee55d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
