Date: Tue, 22 Feb 2005 09:34:33 -0500
From: "Joel Fradkin" <jfradkin@wazagua.com>
Subject: Re: problem inserting local characters ...
In-reply-to: <421B3650.2020203@logi-track.com>
To: "'Markus Schaber'" <schabios@logi-track.com>,
	"'Garry'" <gkg@gmx.de>
Cc: <pgsql-sql@postgresql.org>
Message-id: <000801c518eb$a1460930$797ba8c0@jfradkin>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

I had a similar problem myself and found if I used SQL_ASCHII for the =
data
base I could insert my data.

I understand however that it basically means the database does not know
anything about encoding and therefore stuff like upper does not work on =
the
extended chars.

I ended up changing to sql_aschii so both my inserts and backup and =
restore
work, realizing I am giving up some functionality.

Joel Fradkin
=20
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel.  941-753-7111 ext 305
=20
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
=A9 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
 This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized =
review,
use, disclosure or distribution is prohibited.  If you are not the =
intended
recipient, please contact the sender by reply email and delete and =
destroy
all copies of the original message, including attachments.
=20

=20

-----Original Message-----
From: pgsql-sql-owner@postgresql.org =
[mailto:pgsql-sql-owner@postgresql.org]
On Behalf Of Markus Schaber
Sent: Tuesday, February 22, 2005 8:41 AM
To: Garry
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] problem inserting local characters ...

Hi, Garry,

Garry schrieb:

> Trying to do this insert, I get an error on both the values
> "TelefonGesch=E4ft" and "Firmenstra=DFe":
>=20
> FEHLER:  ung=C3=BCltige Byte-Sequenz f=C3=BCr Kodierung =
=C2=BBUNICODE=C2=AB: 0xe165

This sounds as your database was created in unicode (utf-8).

> (the 0xe165 differs between the two; the fields in question are =
regular
> type "text" fields)
>=20
> Looks like I'm having some trouble with unicode encoding ... The
> characters I have are regular 8bit ASCII chars ... How can I fix this?

No, 8bit ASCII does not exist. ASCII always is 7 bit. As your error
message is in German, I suspect your data is encoded in LATIN1 or LATIN9
(their only difference is the EUR symbol in the latter one).

Can you try to add the following command before your insert statements:

set client_encoding to latin1;

HTH,
Markus

--=20
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 z=FCrich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com