Subject | Re: Index tales - part 2 - Keyword FTS |
---|---|
Author | m_theologos |
Post date | 2006-10-09T16:29:23Z |
--- In Firebird-Architect@yahoogroups.com, Jim Starkey <jas@...>
wrote:
a general (web) search engine. For instance, I use 3 custom-made
keyword full text search engines using data stored in FB which are
near real-time in their searches but only one from the apps which
uses these (shared) engines does this on multiple fields. No one does
its search on multiple tables.
And if someone wants to do a search on multiple fields then he'll
index these fields and use, for example, NAME KEYWORD = 'John' OR
NICKNAME KEYWORD = 'Jim'. I don't see any problem in this. Or perhaps
I'm missing something?
hth,
m. th.
wrote:
>your
> m_theologos wrote:
> > Hi,
> >
> > Studying a little the FB indexes and some issuses about when the
> > indexes are 'good' or 'bad' I have some small ideeas to put in
> > attention. (I broke this thema in more independent messages).Why? IMHO, I think that are much more applications to FTS rather than
> >
> > 1. Keywords
> >
> > Defining a structure like:
> >
> > CREATE KEYWORD INDEX IDX1 ON T1(TextField1) SEPARATORS '
> > .,!@#$%^&*()' MIN_LETTERS 2 BANNED_WORDS 'AND', 'OR', 'THE' ...
> >
> >
> Text search needs to be multi-table and multi-field to be useful.
>
a general (web) search engine. For instance, I use 3 custom-made
keyword full text search engines using data stored in FB which are
near real-time in their searches but only one from the apps which
uses these (shared) engines does this on multiple fields. No one does
its search on multiple tables.
And if someone wants to do a search on multiple fields then he'll
index these fields and use, for example, NAME KEYWORD = 'John' OR
NICKNAME KEYWORD = 'Jim'. I don't see any problem in this. Or perhaps
I'm missing something?
hth,
m. th.