Thunderstone Support Forums

We want the best bet feature to return results only when ALL words in keywords column are present in the query.

Right now best bet uses matches which is not something we can use because of the unique nature of our application. For example if we have keywords set to 'loan processing' then we want to show best bets only when the query is any of the following forms:

loan processing, processing loan, processing loans, loans processing,xyz loan abc processing, abc processing xyz loan .....................

can't uses matches (we don't want to return best bets when someone types in loan.It is too general term and it would not have any relevance to the query as such). Can't use eq (as you can see word order and proximity are not important, what is important is ALL WORDS). I am willing to repeat the description, title etc. by having only one keyword in keywords box. But we do need best bets to do something like what i mentioned above. I don't know how to accomplish this. Help is greatly appreciated.

In the query against the bestbet table use LIKEIN, and create a metamorph counter index on it.

don't know how to do the second part (never done it). Could you please elaborate? Say i create index from command line then how to use the index in the query?

See if this helps
http://thunderstone.master.com/texis/ma ... ex%22&s=SS

what would be the name of the index?

Like any other index, you can call it whatever you want (within the naming conventions of sql indices).

Pefect. One thing though... in the search settings the word forms is set to 'plural and possesives'. Using likein doesn't return results when someone has used plural/possesive of Keywords however the regular results are returned as expected..

Is this by nature of likein... what's the way around it?

Another thing I just noticed.. if I have a keyword called 'e-statement' and someone types in e-statement as query the best bets don't return any results. But if the keyword is estatement and someone types in estatement ... it works...this needs to be fixed in our case...

Any idea whether the likein issues I mentioned are addressable or not...???

Currently LIKEIN always runs with suffix processing
disabled. I did try the e-statement example and it
seemed to work for me.

1) When you say suffix processing disabled do you mean that e-statement=e-statement but e-statement!=e-statements? I need the suffix processing enabled, how can I do that?

2) It doesn't work for me. Can you tell me how you tried it?

Thank you.