Re: Encoding using the Frontend/Backend Protocol TCP/IP - Mailing list pgsql-general

From Raimon Fernandez
Subject Re: Encoding using the Frontend/Backend Protocol TCP/IP
Date
Msg-id A86C9188-4DAC-4EC4-86BD-0B483287BC71@montx.com
Whole thread Raw
In response to Re: Encoding using the Frontend/Backend Protocol TCP/IP  (Kovalevski Andrei <kovalevski.andrei@gmail.com>)
Responses Re: Encoding using the Frontend/Backend Protocol TCP/IP  (Raimon Fernandez <coder@montx.com>)
List pgsql-general
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 ...



> Can you post here the string and its' encoded version?
>

Original string:
Q

pgsql-general by date:

Previous
From: Sam Mason
Date:
Subject: Re: obtaining ARRAY position for a given match
Next
From: Scott Bailey
Date:
Subject: Re: obtaining ARRAY position for a given match