I have read the pg 9.1 doc's about full text search, rambled about the web a
bit looking for related articles, and had good experiences implementing
lightweight prototypes. Now I can sense the depth of the water as I try to
determine a solid approach for implementation.
I would be most gratefu
APseudoUtopia,
you invented your own query language, so you should write your own
function, which transforms user's query to ::tsquery, if to_tsquery()
and plainto_tsquery() doesn't satisfy your input language.
Notice, that phrase search will be able only in 8.5 version.
Oleg
On Fri, 4 Sep
Hello,
I'm working on setting up a full-text search for some descriptions
stored in my database. I'm running pg 8.4.
>From what I can tell, there are two functions. One function,
to_tsquery(), requires that boolean operators (&, |, !) are between
every word. The other function, plainto_tsquery()
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 the
full-text ind
"Poul L. Christiansen" <[EMAIL PROTECTED]> writes:
>
> I convert the characters - e.g. ø will be converted to ø When I
> do a search, i just replace the search string the same way. The only
> problem that could arise is when people search for the word "slash", but
> I guess you could avoid searc
Gunnar R|nning wrote:
>
> "Poul L. Christiansen" <[EMAIL PROTECTED]> writes:
>
> > I chose to use a 3rd party product (Verity) for full text indexing even
> > though I would prefer to use PostgreSQL for fti.
>
> How is the support for Danish in Verity now ?
I convert the characters - e.g. ø w
