Re: ConText and soundex

Actually, I hadn't thought about how ConText would handle multiple words in a soundex query. This is something I'll have to consider later. Thanks.

However, I still have my problem. Most of the searching I'm doing (at least now) is single word searches. Here's the perfect example of what I'm working with:

Looking at the view that was generated on indexing, there are 23 words that have the same soundex as 'excedrin' (E236). When I do a ConText soundex query on 'excedrin' (e.g., "contains(item_desc, '!excedrin', 0) > 0"), I get 121 rows returned. However, when I do a ConText soundex query on a word that has the same soundex (like the common misspelling 'excedren'), but is not in the column, 0 rows are returned.

Thanks for the quick response.

-Joe

In article <925454480.24374.0.nnrp-04.9e984b29_at_news.demon.co.uk>, jonathan_at_jlcomp.demon.co.uk says...
> I' sure you've thought of this, but it is
> possible for
>
> soundex(column) = soundex('myword')
>
> even though the context index gives no
> return. e.g. (and I'm making up the soundex
> from memory here, not using the function).
>
> soundex('beer lid') = soundex('ballad')
>
> but the contexted soundex(beer) is separated
> from the context soundex(lid), so soundex(ballad)
> will not find either.
>
> Having said that, I have just come across a
> terrific bug in 'sectioned' documents that
> causes an internal query strategy ($ in this
> case) to go wrong if the expansion gives
> more than one value. Fixed in 8.1
>
> --
>
> Jonathan Lewis
> Yet another Oracle-related web site: www.jlcomp.demon.co.uk
>
>
>
>
>
Received on Mon May 03 1999 - 08:40:21 CDT