> > However, the query isn’t going to be very efficient, since it’ll be > generating the entire result set, sorting it, and then throwing away the > results outside the current page. It may be better for you to keep the > entire result set in memory and just display the relevant portions. >
Results count could be over 5000 (or more in future). Without 'sortDescriptors', I may have to write following views. emit(@[project,archived,lastModified],@[email,status]) emit(@[project,archived,title],@[email,status]) emit(@[project,archived,responsible],@[email,status]) emit(@[project,archived,dueDate],@[email,status]) emit(@[project,archived,map,lastModified],@[email,status]) emit(@[project,archived,map,title],@[email,status]) emit(@[project,archived,map,responsible],@[email,status]) emit(@[project,archived,map,dueDate],@[email,status]) I'll still have to use 'postFilter' on the "value" objects. Will the query going to be inefficient even in this case? Not using "postFilter" is going to result in lot of views (see here https://friendpaste.com/2aNqHn0Hg8mwLHgTsDuRuC ) emit(@[project,email,status],@1) emit(@[project,status,email],@1) And, I was wondering if there is any way to avoid writing two views for above case? I only swapped index of objects inside key array. -- 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/6ee90632-9270-4372-8ac8-05c16047fd74%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
