Request a Demo
Home   >   mailing lists

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 - Mailing list pgsql-general

From Mike Rylander
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
Msg-id [email protected]
Whole thread Raw
In response to 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  (Tom Lane <[email protected]>)
List pgsql-general
Tree view 
On Apr 6, 2005 10:22 PM, Tom Lane <[email protected]> wrote:
> David Gagnon <[email protected]> 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
[email protected]
GPLS -- PINES Development
Database Developer
http://open-ils.org

pgsql-general by date:

Previous
From: Chris Smith
Date:
Subject: Re: using limit with delete
Next
From: Alvaro Herrera
Date:
Subject: Re: using limit with delete