| From: | Raimon Fernandez <coder(at)montx(dot)com> |
|---|---|
| To: | Raimon Fernandez <coder(at)montx(dot)com> |
| Cc: | Kovalevski Andrei <kovalevski(dot)andrei(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Encoding using the Frontend/Backend Protocol TCP/IP |
| Date: | 2009-11-19 18:01:53 |
| Message-ID: | 322BBEA5-A328-4197-971E-95359D8FD7F3@montx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
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 some characters 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,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-11-19 18:05:19 | Re: obtaining ARRAY position for a given match |
| Previous Message | Scott Bailey | 2009-11-19 17:52:47 | Re: obtaining ARRAY position for a given match |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kovalevski Andrei | 2009-11-19 20:21:40 | Re: Encoding using the Frontend/Backend Protocol TCP/IP |
| Previous Message | Raimon Fernandez | 2009-11-19 17:13:42 | Re: Encoding using the Frontend/Backend Protocol TCP/IP |