Re: full text searching

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, Gunnar R|nning <gunnar(at)candleweb(dot)no>
Cc: Mitch Vincent <mitch(at)venux(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: full text searching
Date: 2001-02-08 02:54:56
Message-ID: 3.0.5.32.20010208105456.0091a100@192.228.128.13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

At 11:40 AM 07-02-2001 -0600, Thomas T. Thai wrote:
>On 7 Feb 2001, Gunnar R|nning wrote:
>>
>> Since we're only doing exact searches, the index is utilized. But the
>> quality isn't good enough - I would love to have language sensitive
>> searches. "car" should match "cars" but not cartography and "ship"
>> should/could match "boat" etc.
>
>you can use ispell prefix/suffix for searching base words.

Sometimes I want it literal too. e.g. I'm searching for car I want car and
nothing else.

What I figured first was to create yet another dictionary of meanings.

Where ship is converted to meaning1 (verb), meaning2 (noun), etc.
And boat is converted to meaning2 (noun).

But then boat is not really the same as ship. So they should actually be
separate meanings maybe linked by a weight. Maybe we should make use of
Postgresql's polygon stuff, and stick a boat polygon somewhere where it
intersects a ship polygon and a canoe polygon.

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 stuff at the client (do
multiple searches if necessary).

Cheerio,
Link.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Anthony E . Greene 2001-02-08 08:03:57 Re: Import Performance
Previous Message Brett W. McCoy 2001-02-08 02:37:48 Re: monitoring running queries?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-08 03:15:02 PL/pgsql EXECUTE 'SELECT INTO ...'
Previous Message Vince Vielhaber 2001-02-08 01:46:30 Re: preproc.y error