Subject: Re: UTF characters compromising data import.
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=utf-8
From: Gavin Beau Baumanis <gavinb@thespidernet.com>
In-Reply-To: <ij5j2v$t8v$1@reversiblemaps.ath.cx>
Date: Sun, 13 Feb 2011 22:08:41 +1100
Cc: pgsql-sql@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <54974F5C-F995-4980-96CE-87956639C55C@thespidernet.com>
References: <DB66CD37-D380-4C8A-8239-E90B5BD95073@palcare.com.au>
	<ij5j2v$t8v$1@reversiblemaps.ath.cx>
To: Jasen Betts <jasen@xnet.co.nz>

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:
>=20
>> 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.   =20=

>=20
> if you run it through =20
>=20
>  iconv --from-code=3DASCII -to-code=3DUTF8 -c
>=20
> 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.
>=20
> perhaps you can figure it out by observation?
>=20
> --=20
> =E2=9A=82=E2=9A=83 100% natural
>=20
> --=20
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql