From: | Alexander Presber <aljoscha(at)weisshuhn(dot)de> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tsearch2: casting text to tsquery |
Date: | 2005-11-16 13:16:08 |
Message-ID: | E84E7D11-0C7C-43B2-A10C-59963254A6CC@weisshuhn.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Am 16.11.2005 um 13:52 schrieb Oleg Bartunov:
> On Wed, 16 Nov 2005, Alexander Presber wrote:
>
>> Hello,
>>
>> I have a question that arose while using tsearch on a large
>> database of book information.
>>
>> In order to inject unstemmed + stemmed versions of searchstrings
>> into a query we want to cast an expression of type text to tsquery.
>> Unfortunately
>>
>> SELECT 'word'::tsquery
>>
>> (where the literal 'word' is of type 'unknown' seemingly) works
>> just fine while e.g.
>>
>> SELECT ('word' || '&fullword')::tsquery
>>
>> or, simpler
>>
>> SELECT 'word&fullword'::text::tsquery
>>
>> gives
>>
>> ERROR: cannot cast type text to tsearch2.tsquery
>>
>> How can we work around that? Thanks for any help
>
> no workaround needed. to_tsquery provides everything you need. If
> you want fancy-shmancy solution you could always write wrapper
> around tsquery, but
> I doubt you enter queries by hand, so why do you bothering ?
No. No fancy-shmancy solution needed, just one that works.
I do not see a way to include both a stemmed and unstemmed version of
a string into a tsquery.
Can you give an example, please?
Thanks
Alex
P.S. I have read the documentation (twice.)
>>
>> Sincerely yours
>> Alexander Presber
>>
>>
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 6: explain analyze is your friend
>
> Regards,
> Oleg
> _____________________________________________________________
> Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
> Sternberg Astronomical Institute, Moscow University (Russia)
> Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
> phone: +007(095)939-16-83, +007(095)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Thies C. Arntzen | 2005-11-16 13:20:45 | Re: shouldn't postgres know the numer of rows in a (sorted) result-set before returning the first row? |
Previous Message | Richard Huxton | 2005-11-16 13:07:55 | Re: shouldn't postgres know the numer of rows in a (sorted) |