[Please keep the list CCd]
On Thu, Apr 14, 2011 at 8:42 AM, Durumdara <durumdara@gmail.com> wrote:
> Dear Dave!
>
> 2011/4/14 Dave Page <dpage@pgadmin.org>:
>> On Thu, Apr 14, 2011 at 7:58 AM, Durumdara <durumdara@gmail.com> wrote:
>>> Dear Developers!
>>>
>>> I found some problem in PGAdmin. V1.12.1, PG 9.0, Win7/X64.
>>> I have a test table with "text" field.
>>> I fillup this field with chr(1)...chr(255), so it contains 255 characters.
>>>
>>> When I try to see this table, I got error:
>>>
>>> ERROR: character 0x81 of encoding "WIN1250" has no equivalent in "UTF8"
>>>
>>> ********** Error **********
>>>
>>> ERROR: character 0x81 of encoding "WIN1250" has no equivalent in "UTF8"
>>> SQL state: 22P05
>>
>> That error comes from PostgreSQL, and is entirely expected if you try
>> to store non-printable characters in a text column, and then convert
>> it to UTF-8 (which is what happens when pgAdmin requests data).
>> PostgreSQL is extremely strict about enforcing the correctness of
>> unicode data.
>
> Interesting, because the local is Win1250, and the database is Win1250
> too... :-(
>
> Is it PG bug?
Assuming everything that is legal in win1250 does map to something in
utf-8, then it sounds to me like PG isn't being as strict about
enforcing the correctness of win1250 strings as it does utf-8.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
