Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion

From: Mike Rylander <mrylander(at)gmail(dot)com>
To: David Gagnon <dgagnon(at)siunik(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
Date: 2005-04-07 02:13:42
Message-ID: b918cf3d05040619136bee6fb1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Apr 6, 2005 10:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Gagnon <dgagnon(at)siunik(dot)com> writes:
> > So am I right ? Is Postgresql using UTF-8 and don`t really understand
> > UNICODE file (UCS-2)? Is there a way I can make the COPY command with a
> > UNICODE UCS-2 encoding
>
> Postgres only supports UTF-8, not any other encoding of Unicode. Sorry.
>

You can use iconv to convert the file on a *nix-like system, and there
may even be a cygwin build if you're on Windows.

http://www.gnu.org/software/libiconv/

--
Mike Rylander
mrylander(at)gmail(dot)com
GPLS -- PINES Development
Database Developer
http://open-ils.org

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2005-04-07 02:20:07 Re: using limit with delete
Previous Message Chris Smith 2005-04-07 02:11:26 Re: using limit with delete