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

Re: full text search, utf8

From: alexander lunyov <lan(at)zato(dot)ru>
To: pgsql-ru-general(at)postgresql(dot)org
Subject: Re: full text search, utf8
Date: 2009-06-04 05:30:36
Message-ID: 4A275BFC.1090902@zato.ru (view raw or flat)
Thread:
Lists: pgsql-ru-general
Andrew Boag wrote:
>> This error happening also when i'm trying to CREATE TEXT SEARCH
>> DICTIONARY:
>>
>> ports=# CREATE TEXT SEARCH DICTIONARY ruispell (
>> ports(#     TEMPLATE = ispell,
>> ports(#     DictFile = russian,
>> ports(#     AffFile = russian,
>> ports(#     StopWords = russian
>> ports(# );
>> ERROR:  неверная последовательность байт имя кодировки "UTF8": 0xd1
>> ПОДСКАЗКА:  This error can also happen if the byte sequence does not
>> match the encoding expected by the server, which is controlled by
>> "client_encoding".
>> ports=#
>>
>> All data in table populated with perl script that read text file in
>> UTF8 and make INSERTs, and i think if there was illegal character,
>> error would appear after INSERT.
> я с вами согласен, а все равно попробовал бы конверт исходной текст до
> INSERT
> 
> *iconv* -c -t utf8 blah.sql > blah.sql.recode
> 
>  (-c значит - omit illegal UTF8 char)

сконвертировал и словари (взял от openoffice), и файл с данными (csv) с 
ключом -c, та же история.

-- 
alexander lunyov

In response to

pgsql-ru-general by date

Next:From: Nikolay SamokhvalovDate: 2009-06-04 05:36:06
Subject: Re: full text search, utf8
Previous:From: alexander lunyovDate: 2009-06-04 05:19:34
Subject: Re: full text search, utf8

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