Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of torsteinkrausework@gmail.com
 designates 209.85.160.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=SKqAxwUlLPAuivPtIKgv4IITHTO+MD/vemkeRHVkd5tM8jq+JDu1By5+j1B62rk3BT
         PnWVo1MRisg4mETmepOMxhYqa1UkI4zx99pdyF/drn+75b/huYdPAMYARmqx47TdBkpS
         /N+uF1jc9RSmd6QTuuxoW1fAZi7VYx3CDqsXg=
Message-ID: <4DDF6BEE.8070907@gmail.com>
Date: Fri, 27 May 2011 17:16:30 +0800
From: Torstein Krause Johansen <torsteinkrausework@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.15) Gecko/20110402 Icedove/3.1.9
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Complex queries & results
References: <4DDDFD4E.9060701@gmail.com>
 <BANLkTimxsnRiAJh=+c=YWSbYxv1ba51e_w@mail.gmail.com>
 <4DDF164A.7030009@gmail.com>
 <FF823898F63A415F8CCB2EB8D4D2B48D@rgabostyle.com>
In-Reply-To: <FF823898F63A415F8CCB2EB8D4D2B48D@rgabostyle.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi there,

On 27/05/11 16:01, Gabor Ratky wrote:
> The order of your components of your keys matter. There is no way to ignore the first element of your key. You should instead reorder your keys based on what you're trying to count / query.
>
> emit([created_at, a_name, one_id, another_id]);
>
> and querying with:
>
> ?group=true&group_level=2&startkey=["2011-05-26"]&endkey=["2011-05-27", {}]
>
> results in:
>
> {
>   "key": ["2011-05-26", "Lisa"],
>   "value": 1
> },
> {
>   "key": ["2011-05-26", "John"],
>   "value": 2
> },
> {
>   "key": ["2011-05-27", "John"],
>   "value": 1
> }
>
> You can of course emit not just days, but also weeks, months, quarters if that's what you always want. If it arbitrary and you need to aggregate the names afterwards from this smaller set, yo should do it in the client (whoever calls CouchDB to get this information out).

Mhmm, ok, thanks for explaining this.

It means though, that for every unique time stamp that a_name has an 
entry, there will be a corresponding count returned (like the three you 
listed above).

Hence, if a_name has 1000 entries at slightly different times within the 
time range I'm searching for (my created_at includes seconds), I will 
get 1000 such entries back.

> tldr; The elements and order of the keys determines the order of the index and you can only filter for a contiguous part of that index with startkey / endkey.

Ok, thanks a lot for your confirmation!

Cheers,

-Torstein