On Dec 30, 2007 11:43 PM, Gavin <[EMAIL PROTECTED]> wrote:
> Hi,
> In the web application we are developing a user can add the the
> proficiency of a given language such as
>
> English:- Reading, Good
> Writing, Average
> Speaking, Good
>
> French:-
On Dec 31, 2007 8:58 AM, Britske <[EMAIL PROTECTED]> wrote:
> Moreover, I realized that I'm using an xsl-transform in the post-processing
> phase. This would contribute to the high cost I'm seeing as well I think.
> Can this XSL-transform in general be considered small in relation to the
> abovemen
I imagine then that this "scanning-cost" is proportional to the number of
stored fields, correct?
I tested this with generating a second index with 1/10th of the
product-variants (and thus 1/10th) of the stored fields. However I really
don't see the expected (at least by me) drop in post-process
Hi Otis,
I don't really see how this would minimize my number of fields.
At the moment I have 1 pricefield (stored / indexed) and 1 multivalued field
(stored) per product-variant. I have about 2000 product variants.
I could indeed replace each multivalued field by a singlevaluedfield with an
id
