Re: Encoding using the Frontend/Backend Protocol TCP/IP

Поиск
Список
Период
Сортировка
От Raimon Fernandez
Тема Re: Encoding using the Frontend/Backend Protocol TCP/IP
Дата
Msg-id 322BBEA5-A328-4197-971E-95359D8FD7F3@montx.com
обсуждение исходный текст
Ответ на Re: Encoding using the Frontend/Backend Protocol TCP/IP  (Raimon Fernandez <coder@montx.com>)
Ответы Re: Encoding using the Frontend/Backend Protocol TCP/IP
Список pgsql-general
On 19/11/2009, at 18:13, Raimon Fernandez wrote:

>
> On 19/11/2009, at 17:27, Kovalevski Andrei wrote:
>
>> Hi
>>
>> could it be that you have errors in your UTF8 string? For example you might use UTF16 encoding, it can explain why
somecharacters force errors but others are not. 
>
> It only happens with values like àéïçñ I think UTF8 can handle this ...


yes, It can handle it ...

if I send the decoding by hand in a very simple update, it works, so there's something with UTF8 conversion that dosn't
work... 

for example, instead of sending Ç i send their equivalent in UTF8 &HC3+&H87 and it works ...

thanks,

regards,




В списке pgsql-general по дате отправления:

Предыдущее
От: Scott Bailey
Дата:
Сообщение: Re: obtaining ARRAY position for a given match
Следующее
От: Sam Mason
Дата:
Сообщение: Re: obtaining ARRAY position for a given match