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

Re: latin1 unicode conversion errors

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: latin1 unicode conversion errors
Date: 2006-02-03 11:59:00
Message-ID: 200602031159.k13Bx0o12148@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
My guess is that it was coded by someone different and needs to be made
consistent.

---------------------------------------------------------------------------

Kris Jurka wrote:
> 
> Why is latin1 special in its conversion from unconvertible unicode data? 
> Other latin character sets add a warning, but latin1 errors out.
> 
> jurka=# create database utf8 with encoding ='utf8';
> CREATE DATABASE
> jurka=# \c utf8
> You are now connected to database "utf8".
> utf8=# create table t(a text);
> CREATE TABLE
> utf8=# insert into t values ('\346\231\243');
> INSERT 0 1
> utf8=# set client_encoding = 'latin2';
> SET
> utf8=# select * from t;
> WARNING:  ignoring unconvertible UTF-8 character 0xe699a3
>   a
> ---
> 
> (1 row)
> 
> utf8=# set client_encoding = 'latin1';
> SET
> utf8=# select * from t;
> ERROR:  could not convert UTF8 character 0x00e6 to ISO8859-1
> 
> Kris Jurka
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Salman RazzaqDate: 2006-02-03 12:30:16
Subject: Need Help In arrays
Previous:From: Kris JurkaDate: 2006-02-03 11:22:46
Subject: latin1 unicode conversion errors

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