Skip site navigation (1) Skip section navigation (2)

Re: Using HStore type in TSearch

From: Łukasz Dejneka <l(dot)dejneka(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Using HStore type in TSearch
Date: 2010-03-29 17:05:44
Message-ID: 4df5da451003291005u6722397ew86c73107884adb8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2010/3/29 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> =?ISO-8859-2?Q?=A3ukasz_Dejneka?= <l(dot)dejneka(at)gmail(dot)com> writes:
> > What I want to do is to use HStore data type (namely the HStore keys) in
> > TSearch. I don't want use TSVector and the original ts_match_vq function,
> > because I want to be able to control exact values that are passed to the
> > search and not use their lexemes.
>
> If that's what you're after, why don't you set up a text search
> configuration in which the parser/dictionary are trivial and do no
> transformations of the strings (beyond perhaps splitting at whitespace)?
> Seems a lot easier than constructing your own datatype and all the
> required support functions.
>
>                        regards, tom lane
>

Hi,

Thanks for the idea, but unfortunately it's not an option for me... This
needs to be expendable in the near future, so need to be a coded as a
separate function :/

In response to

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2010-03-29 17:16:04
Subject: Re: Parallel pg_dump for 9.1
Previous:From: Pavel StehuleDate: 2010-03-29 16:47:04
Subject: Re: proposal - structured funcid and lineno as new fields in error message

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group