Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> Sometimes I want it literal too. e.g. I'm searching for car I want car and
> nothing else.
Of course, you want this as well.
> In the end it seems too complex. I'm starting to think it may be better to
> keep things literal but fast, and do the smart
On 7 Feb 2001, Gunnar R|nning wrote:
> It is really not based on the FTI code in PostgreSQL, since with we started
> out with a Progress database last year before porting to PostgreSQL. The
> idea is the same though, a separate lookup table containing the words for
> exact matching. Last time I ha
"Mitch Vincent" <[EMAIL PROTECTED]> writes:
> > I've been using a variant of the FTI system in an application, but this is
> > far from sufficient when it comes to matching. Speed is OK, but the
> quality
> > of the results could have been a lot better.
>
> Really? How are you using it? If it's
"Mitch Vincent" <[EMAIL PROTECTED]> writes:
> Well, the search engine isn't the database, IMHO. The search "engine" is
> your application... The database will go get anything you tell it to, you
> just have to know how to tell it and make sure that your application tells
> it in the correct way.
> Well you wouldn't want to start building these kind of rules in your
> application - better to have them in the search engine. The fulltextindex
> in the contrib package does of course not offer anything like this, it
> would be nice to see a third party addon provide fulltext capabilities for
Another thing..
Full text indexing, last time I checked, was just a trigger/function, you
don't have to rebuild anything that I'm aware of to include it..
-Mitch
> Hi,
>
> OK full text searching. Will the full text index
> catch changes in verb tense? i.e. will a search for
> woman catch wome
> Hi,
>
> OK full text searching. Will the full text index
> catch changes in verb tense? i.e. will a search for
> woman catch women?
>
> I'm researching before I dive in to this later in the
> week so please excuse this incompletely informed
> question: Will I need to rebuild postgresql with t