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 paul.joseph.davis@gmail.com
 designates 209.85.198.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=DLuq5VUrUjPL5nb+d7TFQOVrnGnlByaMbXu/plXPtIOaSSDkixD1fym//TkuZjS2ah
         7B4+L9k1fmCPaqQeCNi/hanwPIhV+ub6+5JsUH1fHmeHZUp5P7jk4Nv7HdKKXCBTWXxL
         DjEkXZKZJHKkGTYLrQEJYg5yL+MIXmCov5b6s=
Message-ID: <e2111bbb0812121313n5bcc633l8e6b78c207626a6c@mail.gmail.com>
Date: Fri, 12 Dec 2008 16:13:50 -0500
From: "Paul Davis" <paul.joseph.davis@gmail.com>
To: user@couchdb.apache.org
Subject: Re: Array key queries
In-Reply-To: <CC49A7EA-6C1B-487D-A36E-FE073C344AFE@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <13ae4dd50812121259r492a925dkf7ee9fe8388a0868@mail.gmail.com>
	 <CC49A7EA-6C1B-487D-A36E-FE073C344AFE@gmail.com>

On Fri, Dec 12, 2008 at 4:09 PM, Adam Kocoloski
<adam.kocoloski@gmail.com> wrote:
> Hi Paul, yes it is.  The startkey/endkey filtering can only select a
> continuous range in the keyspace, and the keys are sorted by the first
> element in the array (first).  If you happened to have row in that view with
> a key [{}, 1], your second query would have suppressed it.
>
> I realize that filtering on an arbitrary position in the array would be
> sweet, but it would be quite a lot more work for the server.  I'm not a
> member of the development team, but I'll bet that kind of functionality will
> only appear if CouchDB's flavor of MapReduce grows support for a remap
> phase.  Best,
>

On a side note, one of my github branches is a custom sort order patch
for views that allows for declaring ascending or descending sort order
for each position in an array key.

> Adam
>
> On Dec 12, 2008, at 3:59 PM, Paul Carey wrote:
>
>> Querying with an array based key produces inconsistent results across
>> different key indexes.
>>
>> For example, consider a view that emits the following keys
>>
>> [0, 0]
>> [0, 1]
>> [1, 0]
>> [1, 1]
>>
>> Querying with startkey=[0, null] and endkey=[0, {}] returns
>>
>> [0, 0]
>> [0, 1]
>>
>> However, querying with startkey=[null, 0] and endkey=[{}, 0] does not
>> return
>>
>> [0, 0]
>> [1, 0]
>>
>> Instead, all rows are returned.
>>
>> Is this the expected behaviour?
>>
>> Thanks
>> Paul
>
>