From: | AI Rumman <rummandba(at)gmail(dot)com> |
---|---|
To: | Christian Ullrich <chris(at)chrullrich(dot)net> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: I cannot insert bengali character in UTF8 |
Date: | 2012-07-20 22:26:50 |
Message-ID: | CAGoODpfcF=0QxxHx2XPkMiUzNMkoe-6MNpz0f9D=7a=h4Wqyog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
WOW. Great informative answer. Thanks.
On Fri, Jul 20, 2012 at 7:11 PM, Christian Ullrich <chris(at)chrullrich(dot)net>wrote:
> * AI Rumman wrote:
>
> I am using database with UTF8 and LC_CTYPE set as default value in
>> Postgresql 9.1.
>> But I cannot insert bengali character in a column.
>>
>> Query Failed:INSERT into tracker (user_id, module_name, item_id,
>> item_summary) values ('1','Leads','353','বাংলা টেস্��...')::ADODB
>> error::->ERROR: invalid byte sequence for encoding "UTF8": 0xe0a62e
>>
>
> E0 A6 2E is not valid UTF-8: 11100000 10100110 00101110
>
> The lead byte indicates that the codepoint consists of three bytes,
> but only the very next byte is a trail byte (10......). The third
> byte is a single character, a period ("."), to be exact.
>
> Setting the MSB on the third byte gives us
>
> 11100000 10100110 10101110 = E0 A6 AE
>
> , which is a valid UTF-8 encoding of U+09AE BENGALI LETTER MA.
>
> Check your input data.
>
> --
> Christian
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-20 22:51:09 | Re: A Better Way? (Multi-Left Join Lookup) |
Previous Message | David Johnston | 2012-07-20 21:49:16 | Re: A Better Way? (Multi-Left Join Lookup) |