X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DD1235529B for ; Thu, 24 Feb 2005 16:06:36 +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 76560-04 for ; Thu, 24 Feb 2005 16:06:34 +0000 (GMT) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by svr1.postgresql.org (Postfix) with ESMTP id A2F45552D4 for ; Thu, 24 Feb 2005 16:06:34 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0ICF00IJCBF7JAA0@vms044.mailsrvcs.net> for pgsql-admin@postgresql.org; Thu, 24 Feb 2005 10:06:45 -0600 (CST) Date: Thu, 24 Feb 2005 11:10:41 -0500 From: "Joel Fradkin" Subject: Re: invalid multibyte character for locale In-reply-to: <24832.1109258150@sss.pgh.pa.us> To: "'Tom Lane'" , "'Bjoern Metzdorf'" Cc: "'Pgsql-Admin (E-mail)'" Message-id: <004801c51a8b$6464c870$797ba8c0@jfradkin> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.153 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200502/286 X-Sequence-Number: 16454 I ended up using SQL_ASCHII and could see lower works fine but on extended chars it does nothing. SO if that's what your shooting for it worked ok for me. I would have preferred to have my encoding Unicode , but don't want to figure out why the odbc driver was not able to insert extended chars. I could insert the extended chars fine in pgadmin and also with .net driver with a encoding = Unicode, but we have lots of asp that will use the odbc driver so I had to go with SQL_ASCHII to avoid getting errors. Joel Fradkin Wazagua, Inc. 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 jfradkin@wazagua.com www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. C 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. -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Thursday, February 24, 2005 10:16 AM To: Bjoern Metzdorf Cc: Pgsql-Admin (E-mail) Subject: Re: [ADMIN] invalid multibyte character for locale Bjoern Metzdorf writes: > Is 8.0 just stricter or is this just a side effect > of your fix for multibyte upper/lower problem for locale != C? Both those statements are true. > If 7.3 and 7.4 behaviour is intended, is there a way to let 8.0 behave > the same? I don't know what behavior you thought you were getting from upper/lower on UTF-8 data in 7.4, but it was surely not correct. If you want to duplicate that misbehavior, try SQL_ASCII with C locale. This does not stop you from storing UTF-8 in your database, mind you --- it just loses validation of encoding sequences and conversion to other schemes. But having said that, upper() should work if the locale matches the encoding. You might take the trouble to trace down exactly what data value it's barfing on. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend