Re: integrated tsearch doesn't work with non utf8 database - Mailing list pgsql-hackers

From Tom Lane
Subject Re: integrated tsearch doesn't work with non utf8 database
Date
Msg-id 12790.1189441497@sss.pgh.pa.us
Whole thread Raw
In response to Re: integrated tsearch doesn't work with non utf8 database  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Teodor Sigaev <teodor@sigaev.ru> writes:
>> I think Teodor's solution is wrong as it stands, because if the subquery
>> finds matches for mapcfg and maptokentype, but none of those rows
>> produce a non-null ts_lexize result, it will instead emit one row with a
>> null result, which is not what should happen.

> But concatenation with NULL will have result NULL, so "Lexized token" column 
> will have NULL as supposed.

Ah, you're right --- objection withdrawn.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: invalidly encoded strings
Next
From: Martijn van Oosterhout
Date:
Subject: Re: invalidly encoded strings