On Fri, Mar 27, 2015 at 9:03 AM, Luca Morandini wrote:
>
> Hope this helps.
>
Thinking about every example at this point is helpful, eve if it doesn't
solve my immediate problem. Thanks everyone for the replies.
I'm currently thinking of combining two views together to solve different
parts
On 26/03/15 07:11, Russell McOrmond wrote:
For most of the hundreds of thousands of keys, the reduce function has
nothing to return -- and I'd like to quickly skip over them and get to the
few keys where I did have something to return.
You should define a way to aggregate the documents prod
On Wed, Mar 25, 2015 at 4:05 PM, Alexander Shorin wrote:
> Why not to make a view which doesn't emits keys with null values?
>
I guess my attempt to quickly describe the problem didn't provide enough
detail.
Coming out of the map, all keys have values. Then in the reduce there is
logic whi
Why not to make a view which doesn't emits keys with null values?
--
,,,^..^,,,
On Wed, Mar 25, 2015 at 10:49 PM, Russell McOrmond
wrote:
>
> This is a beginner question from someone who only installed CouchDB a
> few weeks ago.
>
> What I'm trying to do may be simple, but the current way I'
This is a beginner question from someone who only installed CouchDB a
few weeks ago.
What I'm trying to do may be simple, but the current way I'm doing it
is extremely slow. I have a view where after the work done by the
reduce, most of the keys have no value and I would like to skip them.
