Ok, i'm going to go and implement this solution then. Thanks for the help :)
On Wed, Aug 12, 2009 at 2:11 PM, Avlesh Singh wrote:
> >
> > > multiValued="true" />
> >
> I think this should be good enough with the "number of days since ..." kind
> of data.
>
> Cheers
> Avlesh
>
> On Wed, Aug 12,
>
> multiValued="true" />
>
I think this should be good enough with the "number of days since ..." kind
of data.
Cheers
Avlesh
On Wed, Aug 12, 2009 at 5:26 PM, Constantijn Visinescu
wrote:
> Hmm .. I looked up the transformer class and that should work, thanks for
> the tip :)
>
> Thinking abou
Hmm .. I looked up the transformer class and that should work, thanks for
the tip :)
Thinking about it a bit more, wouldn't it be easier to just add a field like
And use a function in the transformer to converts the day to int (number of
days since jan 1st 2000 or something).
Then if i use the
>
> I'd have to add the year because things might end up reserved far ahead, or
> they might be reserved again on the same day next year.
>
If that is the case, then yes you'll have to take year into account too.
Wouldn't it be terribly inefficient when I have 10million+ documents in my
> index an
On Tue, Aug 11, 2009 at 6:13 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> On Tue, Aug 11, 2009 at 7:08 PM, Constantijn Visinescu
> wrote:
>
> >
> >
> > Room1
> > 2000-08-01T00:00:00Z
> > 2000-08-31T23:59:59Z
> >
> >
> > Room2
> > 2000-08-01T00:00:00Z
> > 2000-08-13T23:59:59Z
> >
Hi,
This seems like a bit of an unconventional suggestion but it just might
work.
I'd have to add the year because things might end up reserved far ahead, or
they might be reserved again on the same day next year.
I do have 2 questions:
1) Wouldn't it be terribly inefficient when I have 10millio
>
> Searches would be for documents (rooms) that don't have certain dates in
> their multi-valued fields for the a particular month.
> E.g if you wanted to find out rooms available on 15th, 16th and 17th of
> August, the query could be:
> q=!(+reserved_dates_August:15 +reserved_dates_August:16
> +r
On Tue, Aug 11, 2009 at 7:08 PM, Constantijn Visinescu
wrote:
>
>
> Room1
> 2000-08-01T00:00:00Z
> 2000-08-31T23:59:59Z
>
>
> Room2
> 2000-08-01T00:00:00Z
> 2000-08-13T23:59:59Z
> 2000-08-20T00:00:00Z
> 2000-08-22T23:59:59Z
>
>
> Now i want to run a query that gives me all documents(rooms) tha
>From what I understood, you need a day level granularity (i.e booked on
15th, 16th and 17th of August) in your indexes. If this is true, then why
even store a "date"? For your use case, I think this should suffice -
Each document will have values like these for this particular field -
reserved_d
