From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Durumdara <durumdara(at)gmail(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Bug? Text field is not viewable in a table... |
Date: | 2011-04-14 07:23:45 |
Message-ID: | BANLkTi=pR__HGQEw_tCsx2197p6LdUx+_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Thu, Apr 14, 2011 at 7:58 AM, Durumdara <durumdara(at)gmail(dot)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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-04-14 07:58:55 | Re: Bug? Text field is not viewable in a table... |
Previous Message | Durumdara | 2011-04-14 06:58:09 | Bug? Text field is not viewable in a table... |