Re: Using text search for locations, or a computed btree index - Mailing list pgsql-admin

From Jaume Sabater
Subject Re: Using text search for locations, or a computed btree index
Date
Msg-id 26819476.7901228411751220.JavaMail.root@zimbra.linuxsilo.net
Whole thread Raw
List pgsql-admin
----- "Jaume Sabater" <jsabater@linuxsilo.net> wrote:

> The guys creating the web site at the company I work for want an
> incremental search for locations. So, I need to find all locations
> that start with Uni, then Unit, then Unite, and so on. Problem is that

Correct: start or contain.

> What I don't know how to do is to just tell tsvector (and tsquery when
> searching) to do what I need and not what I don't need. I can't find a
> way in the online documentation to tell the engine which pieces I want
> from the whole puzzle.

Rereading the configuration example section of the documentation, just thought that most probably PostgreSQL won't be
applyingthe "phases" of normalization that I don't need if I create a new configuration and don't add any dictionary
butthe synonyms one (that would be used for the alternate names of locations). 

Still, not sure how to control the way accented characters are converted. Will tsvector still convert accented
charactersto their non-accented equivalents if I don't specify any dictionary or thesaurus? 

--
Jaume Sabater
http://linuxsilo.net/

"Ubi sapientas ibi libertas"

pgsql-admin by date:

Previous
From: Jaume Sabater
Date:
Subject: Using text search for locations, or a computed btree index
Next
From: Marc Fromm
Date:
Subject: Re: restore a table in a database