Re: db/_all_conflicts

2016-03-29 Thread Adam Kocoloski
Neat stuff. Years ago I actually committed this feature to the codebase using a table scan and then Damien backed it out because of the scalability concern. Glad to see we’re approaching it in a more considered fashion this time around :) One thing we might consider is to maintain a *count* of

Re: db/_all_conflicts

2016-03-29 Thread Robert Kowalski
Hi, good points! > 3.1. An optimisation of 3. would be making this an Erlang view, but that > would come with > the additional security concern of opening up Erlang views. The great thing about Mango is, with an index Mango is faster than JS views as it is Erlang based. And Dale is making a