Re: Full text search ts_heading strange result
| От | Craig Ringer |
|---|---|
| Тема | Re: Full text search ts_heading strange result |
| Дата | |
| Msg-id | 5010FD76.30308@ringerc.id.au обсуждение исходный текст |
| Ответ на | Re: Full text search ts_heading strange result (Johann Spies <jspies@sun.ac.za>) |
| Ответы |
Re: Full text search ts_heading strange result
|
| Список | pgsql-general |
On 07/26/2012 02:14 PM, Johann Spies wrote:
> Hallo Tom,
>
>> I believe the problem is that the one-argument form of to_tsquery() uses
>> the default TS configuration, which you have probably not got set to
>> "simple". For me, the default TS configuration is "english", which will
>> stem "polity" as "politi":
>>
>> regression=# select to_tsquery('(polity & church)');
>> to_tsquery
>> ---------------------
>> 'politi' & 'church'
>> (1 row)
>>
>> However the "simple" configuration doesn't do anything to that lexeme:
> Thanks for the explanation. I am working with a multi-language database
> and that was the reason for using the 'simple' configuration.
>
> I have asked, in an earlier message on this list, advice on how to
> handle full text searches in a multi-language database, but got no
> reaction to it. If there is a better way than using the 'simple'
> configuration in this case, I would gladly try it.
You'll need to store language information alongside each text value if
you want to do anything more sophisticated. If you have mixed languages
within a single text value or if you don't store information about the
language a text value is in then you're largely out of luck.
--
Craig Ringer
В списке pgsql-general по дате отправления: