X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5EF99D1C47A for ; Mon, 11 Aug 2003 22:25:23 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 51191-03 for ; Mon, 11 Aug 2003 19:23:54 -0300 (ADT) Received: from snoopy.oit.edu (snoopy.OIT.EDU [140.211.135.12]) by svr1.postgresql.org (Postfix) with ESMTP id B910FD1C4DF for ; Mon, 11 Aug 2003 19:25:11 -0300 (ADT) Received: from cvc.net (purvine-141-62.oit.edu [140.211.141.62]) by snoopy.oit.edu (8.12.9/8.12.9/OIT-4.0) with ESMTP id h7BMOZWD004043; Mon, 11 Aug 2003 15:24:40 -0700 Message-ID: <3F381888.6040702@cvc.net> Date: Mon, 11 Aug 2003 15:28:24 -0700 From: Dennis Gearon Reply-To: gearond@cvc.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, ru, es-mx MIME-Version: 1.0 To: Bruce Momjian Cc: Oleg Bartunov , Eugeny Balakhonov , pgsql-general@postgresql.org Subject: Re: PostgreSQL References: <200308112144.h7BLiJo03456@candle.pha.pa.us> In-Reply-To: <200308112144.h7BLiJo03456@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/505 X-Sequence-Number: 46922 I think if Postgres were to be completely UTF8 compatible, and as the default configuration, we'd do a lot better against 'the others', and take more of Oracle's market. Bruce Momjian wrote: > Well, I have no mention of this problem in the TODO list, so I would > like to get a good description of why it isn't working. > > Looking at the code, I see upper() is defined in oracle_compat.c (you > would think it would be more standard), and it calls toupper(), so it > probably works on single-bytes encodings, but not multi-byte ones. Is > this correct? is there a way to do multi-byte toupper? Perhaps > converting to wide characters and calling towupper()? > > --------------------------------------------------------------------------- > > Oleg Bartunov wrote: > >>On Mon, 11 Aug 2003, Bruce Momjian wrote: >> >> >>>Not sure. I thought it would work. >>> >> >>No, it doesn't works. Several people already complained about bad >>unicode support. I recall Tatsuo comment some piece of code. >>I have a little page http://www.sai.msu.su/~megera/postgres/utf8.html >>about my experience with UTF8 and cyrillic. >> >> >> >> >>>--------------------------------------------------------------------------- >>> >>>Eugeny Balakhonov wrote: >>> >>>>Hello, all! >>>> >>>>I have a good question for PostgreSQL FAQ. >>>> >>>>How to use string functions (like UPPER()/LOWER()) for non-latin strings? >>>>Why UPPER() function doesn't work with my UNICODE PostgreSQL database which contains non-latin characters (like cyrillic)? >>>>How to make case insensetive search by text field which contains non-latin characters? >>>> >>>>Thanks for your answers! >>>> >>>>Best regards >>>>Eugeny >>> >>> >> Regards, >> Oleg >>_____________________________________________________________ >>Oleg Bartunov, sci.researcher, hostmaster of AstroNet, >>Sternberg Astronomical Institute, Moscow University (Russia) >>Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ >>phone: +007(095)939-16-83, +007(095)939-23-83 >> > >