| From: | Zach Seaman <znseaman(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ken Benson <ken(at)infowerks(dot)com>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
| Date: | 2013-02-07 17:59:08 |
| Message-ID: | CACVtUUut9XpnoV55u3GSGfQ0M6LFsiqqddjsCmE59p45uOYPzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Zach Seaman <znseaman(at)gmail(dot)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.)
*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Swierczek | 2013-02-07 18:02:05 | Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
| Previous Message | Tom Lane | 2013-02-07 17:51:15 | Re: Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Swierczek | 2013-02-07 18:02:05 | Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
| Previous Message | Tom Lane | 2013-02-07 17:51:15 | Re: Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |