Hi Alex,
feedback inline:
On Mon, 2010-07-12 at 12:03 +0200, "Alex J. G. Burzyński" wrote:
> Hi Chantal,
>
> The paging problem I've asked about is that having course-event pairs
> and specifying rows limits the number of pairs returned not the courses
>
> +---+--+-
Hi Chantal,
The paging problem I've asked about is that having course-event pairs
and specifying rows limits the number of pairs returned not the courses
+---+--+++
| id-id | name | town | date |
+---+-
Hi Alex,
I think you have to explain the complete use case. Paging is done by
specifying the parameter "start" (and "rows" if you want to have more or
less than 10 hits per page). For each page you need of course a new
query, but the queries differ only in the parameter value "start" (first
page s
Hi,
So if those are separate documents how should I handle paging? Two
separate queries?
First to return all matching courses-events pairs, and second one to get
courses for given page?
Is this common design described in details somewhere?
Thanks,
Alex
On 2010-07-09 01:50, Lance Norskog wro
Yes, denormalizing the index into separate (name,town) pairs is the
common design for this problem.
2010/7/8 "Alex J. G. Burzyński" :
> Hi,
>
> Is it possible to remove from search results the multivalued fields that
> don't pass the search criteria?
>
> My schema is defined as:
>
>
> required="
