: Despite considerations of stemming and such for "text"
: type fields, is it the case that
: if we have a single value "text" type field,
: will sorting work, though?
correct ... KeywordTokenizer with Filters of your choice should produce a
sortable string of whatever form you desire.
-Hoss
Despite considerations of stemming and such for "text"
type fields, is it the case that
if we have a single value "text" type field,
will sorting work, though?
--tracey
On 9/11/06, Tom Weber <[EMAIL PROTECTED]> wrote:
Thanks also for the "multiValued" explanation, this is useful for
my curr
On 9/11/06, Tom Weber <[EMAIL PROTECTED]> wrote:
Thanks also for the "multiValued" explanation, this is useful for
my current application. But then, if I use this field and I ask for
sorting, how will the sorting be done, alphanumeric on the first
entry for this field ? Until now, I entered mo
Hello Yonik,
You are right about the string stuff, I saw while turning on the
debugging a few minutes ago, that it is splitting the md5 sum up in
several parts, eacht time we have a number after a letter or the
other way round.
Thanks also for the "multiValued" explanation, this is us
On 9/11/06, Tom Weber <[EMAIL PROTECTED]> wrote:
Hello,
have a strange response in a query with sorting.
I sort on a field which is :
I think you probably want a type="string" instead. Text fields have
text analysis (stemming, lowercasing, word splitting, etc) and aren't
used for
