Thanks. My workaround was to create a category on CBLView that creates and runs an async query with a limit of 1. For those views that I need to be indexed immediately, I invoke this category method in response to a kCBLDatabaseChangedNotification. Does this seem like the right approach?
On Friday, December 18, 2015 at 11:47:53 AM UTC-5, Martin Rybak wrote: > > 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/3d560b04-40fb-4113-8a91-5927f5c00eeb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
