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-12 21:14:47 |
Message-ID: | 200602122114.k1CLEl721577@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
OK, yea, it is inconsistent. I changed it do throw a warning instead.
Only patched to 8.2 because it is a behavior change.
---------------------------------------------------------------------------
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
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 1001 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-02-12 21:55:14 | Use cases |
Previous Message | Bruce Momjian | 2006-02-12 21:13:46 | Re: [HACKERS] slow information schema with thausand users, |