Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 - Mailing list pgsql-novice

From Zach Seaman
Subject Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1
Date
Msg-id CACVtUUut9XpnoV55u3GSGfQ0M6LFsiqqddjsCmE59p45uOYPzg@mail.gmail.com
Whole thread Raw
In response to Re: Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
Ok, client encoding is back to LATIN1.

Do I have to sacrifice the readability of these names or is there a way to work around this invalid byte sequence problem?



On Thu, Feb 7, 2013 at 11:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Zach Seaman <znseaman@gmail.com> writes:
> I changed from LATIN1, set my database to UTF8, and my client_encoding is
> UTF8.

> ERROR:  invalid byte sequence for encoding "UTF8": 0xe17320
> ás[space]

No, the client encoding needs to be LATIN1 to read this file.

                        regards, tom lane



--
Zach Seaman
GIS Expert, IRRI-México

Master of Regional & Community Planning
m 55.2247.1740 (México)
m 01.913.4860.832 (U.S.)

pgsql-novice by date:

Previous
From: Nipuna
Date:
Subject: Finding the no of files and directories in a path
Next
From: Michael Swierczek
Date:
Subject: Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1