pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gavin Beau Baumanis <gavinb@thespidernet.com>
To: Jasen Betts <jasen@xnet.co.nz>
Cc: pgsql-sql@postgresql.org
Subject: Re: UTF characters compromising data import.
Date: Sun, 13 Feb 2011 22:08:41 +1100
Message-ID: <54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com> (raw)
In-Reply-To: <ij5j2v$t8v$1@reversiblemaps.ath.cx>
References: <DB66CD37-D380-4C8A-8239-E90B5BD95073@palcare.com.au>
	<ij5j2v$t8v$1@reversiblemaps.ath.cx>

Hi and thanks for the replies,

I have had some luck.
I did find the encoding used originally to create the text files I am trying to import.

I have managed to use the client_encoding environmental variable and then successfully did manage to import the data.

Gavin.




On 12/02/2011, at 8:15 PM, Jasen Betts wrote:

> On 2011-02-08, Gavin Beau Baumanis <beau@palcare.com.au> wrote:
> 
>> I understand the error message - but what I don't know is what I
>> need to set the encoding to - in order to import  / use the data.    
> 
> if you run it through  
> 
>  iconv --from-code=ASCII -to-code=UTF8 -c
> 
> it'll strip out all the non-ascii symbols,  without knowing the
> encoding it's impossible to assign any useful meaning to them.
> This step may render your data useless, it would be much better to
> find out what the encoding should be.
> 
> perhaps you can figure it out by observation?
> 
> -- 
> ⚂⚃ 100% natural
> 
> -- 
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql




view thread (4+ messages)

Message-ID: <54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com>
Permalink:  ../54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com/
Also on:    postgresql.org/message-id/54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: gavinb@thespidernet.com, jasen@xnet.co.nz
  Subject: Re: UTF characters compromising data import.
  In-Reply-To: <54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox