Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of simonmetson@googlemail.com
 designates 74.125.82.180 as permitted sender)
References: 
 <CACPVBY6+myrQ3HRfFejRzcMt5n7eBF+Pi=UHWVK14m3+OgpNCQ@mail.gmail.com>
 <3D8B736F-2D61-4CCC-86EB-78F7DFB20DBD@sri.com>
In-Reply-To: <3D8B736F-2D61-4CCC-86EB-78F7DFB20DBD@sri.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary=Apple-Mail-86B02D77-42DD-4E15-9DAF-4E22555D0DA4
Message-Id: <4009686D-D3C2-4AD2-B047-9B0EBC44C0DD@googlemail.com>
Cc: "<user@couchdb.apache.org>" <user@couchdb.apache.org>
From: Simon Metson <simonmetson@googlemail.com>
Subject: Re: starkey with multiple values not working as expected
Date: Wed, 7 Mar 2012 09:01:10 +0000
To: "user@couchdb.apache.org" <user@couchdb.apache.org>

--Apple-Mail-86B02D77-42DD-4E15-9DAF-4E22555D0DA4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I wrote a bloglet to illustrate this a while back, it's incomplete (I'd like=
 to inline some code examples and use a lucene search to get a 2d query) but=
 might help illustrate how view slicing works: http://drsm79.cloudant.com/vi=
ew-slicing/_design/view-slicing/index.html


On 1 Mar 2012, at 00:25, Jim Klo <jim.klo@sri.com> wrote:

> actually, it's responding exactly as expected.
>=20
> you can't think of complex keys as a boolean "AND", but as a single value.=

>=20
> so...=20
>=20
>> ["2012-01-01T02:07:50.387+0000","97ee813bfe4dbbf80a48b018b20a08bb"]
>=20
> is actually less than ALL your values because of CouchDB's collation rules=
.
>=20
> To explain this to others, I use the idea of turning the key into a senten=
ce.... typically i think of it as you have the last element grouped by the t=
he other elements from left to right.
>=20
> So you have "restaurantids grouped by timestamp" as your key, which means f=
or any given timestamp as a startkey/endkey, the last item in the key will b=
e a restuarantid... if you try rounding your timestamp to the nearest hour i=
n your example you'll see what I mean using your data...=20
>=20
> if you want to look up by restaurantid, order your keys from left to right=
... [restaurantid, timestamp]... which will then order your view first by re=
staurantid, then by timestamp... which gives you "timestamps grouped by rest=
aurantid"
>=20
> you'd then use
>=20
>> restaurant_orders_after_date?startkey=3D["97ee813bfe4dbbf80a48b018b20a08b=
b","2012-01-01T02:07:50.387+0000"]&endkey=3D["97ee813bfe4dbbf80a48b018b20a08=
bb",{}]
>=20
>=20
> - Jim
>=20
> Jim Klo
> Senior Software Engineer
> Center for Software Engineering
> SRI International
>=20
> On Feb 29, 2012, at 3:45 PM, Mathieu Castonguay wrote:
>=20
>> Here is the view:
>>=20
>>   "restaurant_orders_after_date": {
>>       "map": "function(doc) { if(doc.restaurantId &&
>> doc.timeOfLatestStatusChange && doc.status && (doc.status =3D=3D 'ACCEPTE=
D' ||
>> doc.status =3D=3D 'REJECTED')) {
>> emit([doc.timeOfLatestStatusChange,doc.restaurantId], doc._id)}}"
>>=20
>> Execution of the view:
>>=20
>> restaurant_orders_after_date?startkey=3D["2012-01-01T02:07:50.387+0000","=
97ee813bfe4dbbf80a48b018b20a08bb"]&endkey=3D[{},"97ee813bfe4dbbf80a48b018b20=
a08bb"]
>>=20
>> {"id":"6bb4423653c6d9138524c110cf0047fb","key":["2012-01-03T14:00:52.542+=
0000","f98ba9a518650a6c15c566fc6f03dc8d"],"value":"6bb4423653c6d9138524c110c=
f0047fb"},
>> {"id":"6bb4423653c6d9138524c110cf007276","key":["2012-01-03T17:34:49.565+=
0000","97ee813bfe4dbbf80a48b018b20a08bb"],"value":"6bb4423653c6d9138524c110c=
f007276"},
>> {"id":"6bb4423653c6d9138524c110cf006d26","key":["2012-01-03T17:36:31.222+=
0000","97ee813bfe4dbbf80a48b018b20a08bb"],"value":"6bb4423653c6d9138524c110c=
f006d26"},
>> {"id":"6bb4423653c6d9138524c110cf007c76","key":["2012-01-03T17:38:45.485+=
0000","97ee813bfe4dbbf80a48b018b20a08bb"],"value":"6bb4423653c6d9138524c110c=
f007c76"},
>> {"id":"6bb4423653c6d9138524c110cf006119","key":["2012-01-03T17:47:51.637+=
0000","29b384e85adcdf5b2085dadba5018d03"],"value":"6bb4423653c6d9138524c110c=
f006119"},
>> {"id":"6bb4423653c6d9138524c110cf005e51","key":["2012-01-03T18:00:35.185+=
0000","29b384e85adcdf5b2085dadba5018d03"],"value":"6bb4423653c6d9138524c110c=
f005e51"}
>>=20
>> It seems to completly ignore the second value which is the id of the
>> restaurant. I want all orders who's timeOfLatestStatusChange is greater
>> than the current time (in this case "2012-01-01T02:07:50.387+0000") and
>> who's restaurant id is a certain value(in this case
>> "97ee813bfe4dbbf80a48b018b20a08bb").
>>=20
>> Can anyone explain to me why the second parameter seems ignored, I can me=
an
>> I can put "donkey" and it still does the same thing.
>>=20
>> Thank you,
>>=20
>> Matt
>=20

--Apple-Mail-86B02D77-42DD-4E15-9DAF-4E22555D0DA4--