Re: exposing more parse was: Re: tsearch2: setting weights on tsquery

Поиск
Список
Период
Сортировка
От Ivan Sergio Borgonovo
Тема Re: exposing more parse was: Re: tsearch2: setting weights on tsquery
Дата
Msg-id 20081021160305.6e9679ba@dawn.webthatworks.it
обсуждение исходный текст
Ответ на exposing more parse was: Re: tsearch2: setting weights on tsquery  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Ответы Re: exposing more parse was: Re: tsearch2: setting weights on tsquery  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On Tue, 21 Oct 2008 13:20:12 +0200
Ivan Sergio Borgonovo <mail@webthatworks.it> wrote:

> On Tue, 21 Oct 2008 10:29:52 +0200
> Ivan Sergio Borgonovo <mail@webthatworks.it> wrote:
>
> I came across this:
> http://grokbase.com/topic/2007/08/07/general-tsearch2-plainto-tsquery-with-or/r92nI5l_k9S4iKcWdCxKs05yFQk

that's the best thing I came up with:

select * from regexp_replace(
strip(
to_tsvector(
'<a:A href="http://www.google.com">pippo</a> pluto gigio'
))::text,
'\'([^\']*)\'','\\1:A','g');

This actually exploit the parser and you can specify the
configuration.

It would still be nice to be able to directly work with tsvector
and tsquery so people could exploit the parser, lexer etc... and
recycle the config.

I'd thinking something in the line of

for lex in select * from to_tsvector('jsjdjd fdsds')

would be nice.

--
Ivan Sergio Borgonovo
http://www.webthatworks.it


В списке pgsql-general по дате отправления:

Предыдущее
От: "Brandon Metcalf"
Дата:
Сообщение: Re: syncing with a MySQL DB
Следующее
От: "Sergey Konoplev"
Дата:
Сообщение: Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4