On Thu, Apr 14, 2011 at 7:58 AM, Durumdara <durumd...@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. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
