X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 030035536C for ; Wed, 2 Mar 2005 13:47:11 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63958-09 for ; Wed, 2 Mar 2005 13:47:08 +0000 (GMT) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by svr1.postgresql.org (Postfix) with ESMTP id AD550545EE for ; Wed, 2 Mar 2005 13:47:07 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0ICQ003OC8YMR040@vms042.mailsrvcs.net> for pgsql-sql@postgresql.org; Wed, 02 Mar 2005 07:47:11 -0600 (CST) Date: Wed, 02 Mar 2005 08:51:18 -0500 From: "Joel Fradkin" Subject: Re: psql encoding problem In-reply-to: <4223838A.7030904@numerixtechnology.de> To: , Message-id: <000601c51f2e$e9cf49c0$797ba8c0@jfradkin> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.144 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200503/19 X-Sequence-Number: 20498 I had the same issue using odbc, but .net you can use encodeing =3D = unicode, so not sure what you are using to do the connection. Since I am using ODBC with my ASP I had to switch from Unicode to = SQL_ASCHII for my data base. In effect it tells the database you don=92t know about the encoding and = makes some of the routines like upper not work properly on extended chars. 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 T E Schmitz Sent: Monday, February 28, 2005 3:48 PM To: pgsql-sql@postgresql.org Subject: [SQL] psql encoding problem Hello, I am trying to insert the following record: INSERT INTO item (name,retail_price) VALUES ('Cheese Souffl=E9',7.95,); (I presume you see the accented character in *Souffl=E9*) psql comes back with "invalid byte sequence for encoding "UNICODE": = 0xe9" If I do this via DbVisualizer, the record is inserted fine. Is there any way around this problem? --=20 Regards/Gru=DF, Tarlika Elisabeth Schmitz ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster