Re: fts, compond words?

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: "Andrew J(dot) Kopciuch" <akopciuch(at)bddf(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org, Mike Rylander <mrylander(at)gmail(dot)com>
Subject: Re: fts, compond words?
Date: 2005-12-07 19:50:52
Message-ID: Pine.GSO.4.63.0512072248520.13553@ra.sai.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

As Teodor already pointed there is no non-ambiguous solution, or
at least, we don't know it.

Oleg

On Wed, 7 Dec 2005, Andrew J. Kopciuch wrote:

>>> A & (B | (New OperatorTheNextWordMustFollow York))
>>
>
> I had thought about this before myself. Alas I have never had the time to
> properly investigate implementing such a feature.
>
> :(
>
> A & (B | (New + York))
>
> Something like that?
>
>> Actually, I love that idea. Oleg, would it be possible to create a
>> tsquery operator that understands proximity? Or, how allowing a
>> predicate to the current '&' op, as in '&[dist<=1]' meaning "next
>> token follows with a max distance of 1". I imagine that it would
>> only be useful on unstripped tsvectors, but if the lexem position is
>> already stored ...
>>
>
> Would the proximity go in both directions? Or just forward? What about tokens
> that come before? Just a thought.
>
>
>
> Andy
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jlmssilva 2005-12-07 20:03:04 Help on collation and accent sensitivity
Previous Message Jaime Casanova 2005-12-07 18:31:23 Re: Letting a function return multiple columns instead of a single complex one