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 robert.newson@gmail.com
 designates 209.85.214.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=poS++hqsxPI9sqzo7TgDT5ep+B5uqr7oR4T2yeOjXUvSbdoj16rWZJJylIMsjx+vRa
         f2NRvKz9nrtYhlDz7AywlRtsXJOOlv458rU0OXzR3tCG0r+QjLVNkCxX3Hjm3ClTMGAD
         hwpg2zBZGmTKQk1zgaUd1szLP6Pjx8U8yby5k=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=strgjtTEUMDLqrrtqHFTY78NoJ_ANjs4BywrU@mail.gmail.com>
References: <AANLkTim092Pc_xg3tXQqMN4yuMx5uAMpCP3adLH0wK6m@mail.gmail.com>
	<A9DC438D6CAFFF4BBB2995814444088101203EBAA2A6@VS-EX-01.intra.vpro.nl>
	<AANLkTikF5fAKLHjOStWZPaO4gCv1fBuMP8p0+zz_FYLc@mail.gmail.com>
	<AANLkTi=strgjtTEUMDLqrrtqHFTY78NoJ_ANjs4BywrU@mail.gmail.com>
Date: Sat, 12 Feb 2011 15:00:17 +0000
Message-ID: <AANLkTin1-RGQd+bgz-+LjK+T2kHucXA7t5T8ve4Kpgv5@mail.gmail.com>
Subject: Re: date range querying
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

day=3D1 day was a typo *and* pseudocode.

I mean simply that you should increment 'day' by '1 whole day' in the loop.

let's assume day is an integral value from some epoch (0 meaning jan 1
1970, 1 meaning jan 2 1970, and so on).

for (day=3DstartDay; day<endDay; day++) {
  emit(day, null);
}

B.

On 12 February 2011 14:46, Warner Onstine <warnero@gmail.com> wrote:
> I tried that with no success (in fact it completely borked all views
> for that document type and had to delete it to get things working
> again. I may try and monkey around with these two scripts again to see
> what I did wrong.
>
> It really didn't like
> day=3D 1 day
>
> and honestly I'm not even sure what that's supposed to do.
>
> Thanks for the suggestions, I'll let you know if I figure it out. But
> I am seriously thinking about using ElasticSearch to make it a more
> robust searching solution (I have a lot of searching coming up soon).
>
> -warner
>
> On Sun, Feb 6, 2011 at 3:37 PM, Robert Newson <robert.newson@gmail.com> w=
rote:
>> Within couchdb itself, I think you'd have to do as Nils suggested;
>>
>> for (day =3D startDate; day < endDate; day=3D 1 day) {
>> =A0emit(day, null);
>> }
>>
>> then ?key=3D<day I want>
>>
>> Or you could use couchdb-lucene, index startDate and endDate as dates,
>> query with ?q=3DstartDate:[day TO maxdate]&endDate:[mindate TO day]
>> where 'date' is the date you are searching for.
>>
>> B.
>>
>> On Sun, Feb 6, 2011 at 10:31 PM, Nils Breunese <N.Breunese@vpro.nl> wrot=
e:
>>> You could emit a view index entry for every day in the date range of a =
document? This could become inefficient storage-wise if you have large date=
 ranges.
>>>
>>> What exactly "starts returning records that don't match at all"? In wha=
t way are you querying your view? I have to admit I have no idea how I coul=
d get the information you're looking for from that complex key. Also, the e=
mit method takes two arguments AFAIK: a key and a value. You seem to be emi=
tting a single value?
>>>
>>> Nils.
>>> ________________________________________
>>> Van: Warner Onstine [warnero@gmail.com]
>>> Verzonden: zondag 6 februari 2011 22:57
>>> Aan: user@couchdb.apache.org
>>> Onderwerp: date range querying
>>>
>>> Ok, been banging my head against this for a while and having no luck
>>> figuring out the logical way to do this (other than installing
>>> ElasticSearch - which I'll be doing in the near future).
>>>
>>> I have records that have startDate and endDate ranges. I want to query
>>> the view based on today's date. Say I have a record that has a start
>>> date of 1/31/2011 and an end date of 2/13/2011 and I want to find out
>>> which records fall within today's date.
>>>
>>> In other words
>>> 1/31/2011 < 2/6/2011 < 2/13/2011
>>>
>>> How in the world do I do that? I've been trying something like this:
>>> =A0 =A0 =A0 var startDate =3D new Date(doc.startDate);
>>> =A0 =A0 =A0 =A0var endDate =3D new Date(doc.endDate);
>>> =A0 =A0 =A0 =A0var startYear =3D startDate.getFullYear();
>>> =A0 =A0 =A0 =A0var startMonth =3D startDate.getMonth();
>>> =A0 =A0 =A0 =A0var startDay =3D startDate.getDate();
>>> =A0 =A0 =A0 =A0var endYear =3D endDate.getFullYear();
>>> =A0 =A0 =A0 =A0var endMonth =3D endDate.getMonth();
>>> =A0 =A0 =A0 =A0var endDay =3D endDate.getDate();
>>> =A0 =A0 =A0 =A0emit([
>>> =A0 =A0 =A0 =A0 =A0 =A0startYear,
>>> =A0 =A0 =A0 =A0 =A0 =A0startMonth,
>>> =A0 =A0 =A0 =A0 =A0 =A0startDay,
>>> =A0 =A0 =A0 =A0 =A0 =A0endYear,
>>> =A0 =A0 =A0 =A0 =A0 =A0endMonth,
>>> =A0 =A0 =A0 =A0 =A0 =A0endDay
>>> =A0 =A0 =A0 =A0]);
>>>
>>> But as soon as I add in the endYear variable it goes wonky and starts
>>> returning records that don't match at all. Any help is greatly
>>> appreciated.
>>>
>>> -warner
>>> -----------------------------------------------------------------------=
-
>>> =A0VPRO =A0 www.vpro.nl
>>> -----------------------------------------------------------------------=
-
>>>
>>
>