From: | "Cristian Prieto" <cristian(at)clickdiario(dot)com> |
---|---|
To: | "'Douglas McNaught'" <doug(at)mcnaught(dot)org> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: COPY and Unicode... |
Date: | 2005-09-21 21:01:25 |
Message-ID: | 20050921210702.8C8B110558@mail.clickdiario.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks a lot! Your help was very handy!
-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Douglas McNaught
Sent: Miércoles, 21 de Septiembre de 2005 02:39 p.m.
To: Cristian Prieto
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] COPY and Unicode...
"Cristian Prieto" <cristian(at)clickdiario(dot)com> writes:
> Hello, I need to import some amount of data using the COPY command, the
main
> trouble I found is that the Database is in UNICODE format and the data in
> ASCII Latin-1 codepage, when I try to import it, COPY respond with:
>
> ERROR: invalid byte sequence for encoding "UNICODE": 0xe9
> CONTEXT: COPY geoip_location, line 307, column city: "Yaound"
>
> I've been looking into the documentation and I could not found any
reference
> in copy from a distinct codepage than the used by the database, any help?
Are you setting the client_encoding variable before doing the COPY?
-Doug
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Dawid Kuroczko | 2005-09-21 22:22:06 | Re: Slow search.. quite clueless |
Previous Message | David Fetter | 2005-09-21 20:57:05 | Re: YAPC::Israel looking for Perl/Database speakers |