Re: [POC] Mango Catch All Selector

Hi Robert, I'm with you that the easier we can make it for s/o to get started the better. And I think falling back to a full table scan with a log written is a good and easy way to go. I'd even set the log level to info or even warning to make it clear that there's a problem with huge data sets.

Re: [POC] Mango Catch All Selector

Hey all, I meant to reply to the ticket on pouchdb-find but got distracted by the holidays. I wanted to note that the original motivation for rejecting a selector that doesn't have an index was to avoid the specific situation where a user has a query that appears to run quite quickly in

Re: [POC] Mango Catch All Selector

Hi all, Hope everyone enjoyed the holidays! This is the most common mango experience for new users: 1) Syntax issues to create an index. 2) Running into the "no index found" error because his or her query (with and w/o sort) doesn't match the index correctly. 3) We explain

Re: [POC] Mango Catch All Selector

I havent yet started looking into the implementation details, but when using pouchdb-find I have very much always expected that at some point we would analyse the queries and automatically produce an index for them. This seems like a great step in between. On 4 January 2016 at 13:27, Robert

Re: [POC] Mango Catch All Selector

Hi Robert, This is cool. I think it links in with this https://issues.apache.org/jira/browse/COUCHDB-2928 and this https://github.com/nolanlawson/pouchdb-find/issues/138 Cheers

[POC] Mango Catch All Selector

Hi list, I hope you had awesome holidays! The whole holidays I thought about an idea I had and today I implemented a prototype which still has some bugs and isn't complete yet. I want to find out if there is general interest and if it would be worth to spend more time. The problem I am trying