Re: Searching a DB index.. possible?
| От | Moe |
|---|---|
| Тема | Re: Searching a DB index.. possible? |
| Дата | |
| Msg-id | 861fed221002110911q7916b7d1h99c2f8e08473ba80@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Searching a DB index.. possible? (Richard Huxton <dev@archonet.com>) |
| Ответы |
Re: Searching a DB index.. possible?
|
| Список | pgsql-general |
On Thu, Feb 11, 2010 at 6:56 PM, Richard Huxton <dev@archonet.com> wrote:
On 05/02/10 15:48, Moe wrote:This could get expensive if you have a large index.I am trying to figure out how I can introduce full text search "tips"...
tips meaning, like if you start typing Mer ..
then a box with a couple of words underneath comes up, with *Mercedes,
Mercury *and so on :P
I am thinking that the word suggestions needs to come from the already
existing tsearch2 index.
Words that are frequent in the index could be ranked higher as a search tip.
You might want to summarize down to a separate (word,frequency) table. Particularly if you don't want stemming to interfere with your suggestions.
Stemming is ok. That's fine.
How would this normally be implemented? Should I go through my text word by word myself, or the already existing index and copy over to a new table? Not sure how this would be managable. Every change to something would require a word count down, and then a word up after.
See the manuals (full text search) for details on prefix searches - introduced in 8.4 if you really want to go the tsearch route.
I'll look into that.
--
Richard Huxton
Archonet Ltd
В списке pgsql-general по дате отправления: