| From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
|---|---|
| To: | "Mitch Vincent" <mitch(at)venux(dot)net>, "Brett W(dot) McCoy" <bmccoy(at)chapelperilous(dot)net>, "McMillen Tom" <McMillT(at)EU(dot)MWHSE(dot)COM> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Free Text Search |
| Date: | 2001-03-27 10:29:22 |
| Message-ID: | 3.0.5.32.20010327182922.008f0840@192.228.128.13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At 09:38 AM 26-03-2001 -0500, Mitch Vincent wrote:
>Well, full text searching can be accomplished by using any standard SQL
>query (SELECT * FROM whatever WHERE textfield LIKE '%doda%' -- etc).. Full
>text indexing is another story though.. I'll send some links when I get home
>to some code that I've found here and there that looks promising..
Would that GIST thing help? If it does, any ideas how?
So far the way I might resort to is at the application level.
It'll be nice to be able to do a LIKE '%post%' and have it indexed for at
least some tables.
e.g. create index blah on tablename (lower(data) fulltextops)
Cheerio,
Link.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2001-03-27 10:41:40 | Re: [ANNOUNCE] PostgreSQL and PHP - some Great Bridge news |
| Previous Message | Richard Huxton | 2001-03-27 09:42:20 | Re: Inserting possible dublicate unique keys |