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

Re: invalid byte sequence for encoding "UTF8":

From: ries van Twisk <pg(at)rvt(dot)dds(dot)nl>
To: kulmacet101(at)kulmacet(dot)com
Cc: "pgsql-novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: invalid byte sequence for encoding "UTF8":
Date: 2009-01-08 20:16:26
Message-ID: F7B8BE32-CEEF-49FA-946B-DB9FCBC22155@rvt.dds.nl (view raw or flat)
Thread:
Lists: pgsql-novice
On Jan 8, 2009, at 3:08 PM, kulmacet101(at)kulmacet(dot)com wrote:

>>
>> On Jan 8, 2009, at 2:34 PM, kulmacet101(at)kulmacet(dot)com wrote:
>>
>>> All,
>>>
>>> I have a new postgresql<8.3.4> build on linux<CentOS5> with PHP
>>> talking to
>>> this database. If I try and update or insert on data that has  
>>> special
>>> characters I get this error:
>>>
>>> ERROR:  invalid byte sequence for encoding "UTF8": 0xa9
>>> HINT:  This error can also happen if the byte sequence does not
>>> match the
>>> encoding expected by the server, which is controlled by
>>> "client_encoding".
>>> STATEMENT:  UPDATE preferences SET property = $1,preference_value =
>>> $2,comment = $3,topic = $4 WHERE app_hash =
>>> '50e2606ed950e8021d64349b49f4ee48'
>>>
>>> I have read some articles about client_encoding but I do not know
>>> how to
>>> get around this error.
>>>
>>> Any help or support appreciated.
>>> Thanks in advance,
>>> Kulmacet
>>
>>
>>
>>
>> Kulmacet,
>>
>> is your source data also in UTF-8 ?
>>
>> Ries
>>
>>
>>
>>
>>
>> --
>> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-novice
>>
>
> I'm not sure how to determine if the source data is UTF-8. This data  
> is
> coming from a post to a form.



Your website might not be in UTF-8 in that case.

Ries





In response to

Responses

pgsql-novice by date

Next:From: Bastiaan OlijDate: 2009-01-08 21:32:42
Subject: Re: invalid byte sequence for encoding "UTF8":
Previous:From: kulmacet101Date: 2009-01-08 20:08:25
Subject: Re: invalid byte sequence for encoding "UTF8":

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