Hi Jens, Ok, that makes sense. Although in my case, I'm prefixing my queries with the field identifier, which is unique per form, so it would never get mixed up with any results from other forms.
Anyway, makes sense. Thanks, Brendan On Sunday, June 28, 2015 at 5:51:59 PM UTC-6, Jens Alfke wrote: > > > On Jun 28, 2015, at 12:10 AM, Brendan Duddridge <[email protected] > <javascript:>> wrote: > > I guess I'm just looking for a best practice to get the best performance. > One full text query view or multiple full text query views broken up by > some logical grouping within my app (in my case a set of records for a > specific form). > > > I would just structure it the way that makes sense for your app. If you > put everything into one view, you’re probably going to get a ton of false > positives for queries (i.e. places where the words were found but in the > wrong fields of the document) and you’ll have to write extra code and take > extra time to filter those out. > > —Jens > > -- 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/92805c64-ce5a-47b4-a4e7-d82de551930e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
