From: | Gavan Schneider <pg-gts(at)snkmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [NOVICE] Pro blems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
Date: | 2013-02-07 12:08:17 |
Message-ID: | 12876-1360238905-374533@sneakemail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
On Wednesday, February 6, 2013 at 11:56,
2jt6w5k7mt(at)sneakemail(dot)com (Zach Seaman znseaman-at-gmail.com
|pg-gts/Basic|) wrote:
>This a similar question to this one
><http://www.postgresql.org/message-id/4dda42060512140509xe8b130as@mail.gmail.com>,
>so I have encoded a database with LATIN-1 as suggested
>but can't copy a CSV file into a table within the database.
>
I may have missed something here... why would anyone suggest
LATIN-1 in modern times?
UTF-8 will do all of LATIN-1 and everything else as well. Except
for legacy support why would anyone use anything other than
UTF-8? (Of course there are those where UTF-16 is a better
choice for their dominant language use, e.g. chinese.)
Suggest you use UTF-8 database encoding and if there are no
problems importing the .csv stay with UTF-8. OTOH if there are
still problems when using UTF-8, stay with UTF-8 while you work
out what it is in the .csv file that's causing the problem.
Regards
Gavan
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2013-02-07 12:48:40 | Re: Hot Standby has PANIC: WAL contains references to invalid pages |
Previous Message | Geoff Winkless | 2013-02-07 11:50:39 | Re: Re: feature requests (possibly interested in working on this): functional foreign keys |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2013-02-07 15:03:55 | Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
Previous Message | James David Smith | 2013-02-07 12:05:10 | Re: Installation 8.4 > 9.1 |