Thanks a lot! Your help was very handy! -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Douglas McNaught Sent: Miércoles, 21 de Septiembre de 2005 02:39 p.m. To: Cristian Prieto Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: COPY and Unicode... "Cristian Prieto" <cristian@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
