On Fri, Jan 12, 2007 at 12:18:24AM +0100, Raymond O'connor wrote: > I just got this same error yesterday. I determined it was because my id > field was set to be tokenized. Once I turned off tokenization this > problem went away. I must also mention that I use a modified version of > AAF that allows id to be a string instead. I only receieved this error > when using search by similar results and when searching for an id that > had a letter in it. If the query had only numbers in it, I would not > recieve this error. Kinda strange... > Anyhow, as I said above, the solution for me was to make id untokenized > again (not a big deal, although I would of preferred it to be > tokenized).
the id field is meant to be a unique key identifying a single record. It should not be tokenized in any case. If you need to run searches on it, you should consider adding an additional tokenized field to the index containing the same value. Jens -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
