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

Re: Unicode conversion (Re: [COMMITTERS] pgsql (

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: peter_e(at)gmx(dot)net
Cc: ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unicode conversion (Re: [COMMITTERS] pgsql (
Date: 2000-10-31 00:40:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
> > Add new configure option "--enable-uniconv" that enables automatic
> > code conversion between Unicode and other encodings. Note that
> > this option requires --enable-multibyte also.
> > The reason why this is optional is that the feature requires huge
> > mapping tables and I don't think every user need the feature.
> Can you explain what this does?  Does it mean frontends can use Unicode as
> their character set?

Yes. Here are some examples:

(1) both backend/frontend uses Unicode(actually UTF-8)

$ createdb -E unicode unicode
$ psql unicode
[some sessions follow using UTF-8]

Note that this is not a new functionality as opposite to (2), (3).

(2) backend is ISO8859-2 but frontend is UNICODE

$ createdb -E LATIN2 latin2
$ psql latin2
\encoding UNICODE
[some sessions follows using UTF-8]

Note that if you type in a wrong ISO8859-2 character that could not be
converted to UTF-8, you would get notices something like:

NOTICE:  local_to_utf: could not convert (0x00b4) LATIN2 to UTF-8. Ignored

(3) backend is Unicode but frontend is ISO8859-2

$ createdb -E unicode unicode
$ psql unicode
\encoding LATIN2
[some sessions follow using ISO8859-2]

Same note above...
Tatsuo Ishii

In response to


pgsql-hackers by date

Next:From: Arnold GamboaDate: 2000-10-31 05:25:04
Subject: how good is PostgreSQL
Previous:From: Peter MountDate: 2000-10-30 19:10:37
Subject: Re: Current CVS broken?

pgsql-committers by date

Next:From: petereDate: 2000-10-31 10:22:10
Subject: pgsql/src/backend/nodes (copyfuncs.c equalfuncs.c list.c outfuncs.c read.c)
Previous:From: petereDate: 2000-10-30 17:54:17
Subject: pgsql/src/backend/parser (scan.l)

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