Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4UEOTE98147 for ; Wed, 30 May 2001 10:24:29 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4UENsR21548; Wed, 30 May 2001 10:23:54 -0400 (EDT) To: "tjk@tksoft.com" cc: danlyke@flutterby.com (Dan Lyke), pgsql-sql@postgresql.org Subject: Re: Case Insensitive Queries In-reply-to: <200105301040.DAA26910@smtp3.tksoft.com> References: <200105301040.DAA26910@smtp3.tksoft.com> Comments: In-reply-to "tjk@tksoft.com" message dated "Wed, 30 May 2001 03:40:39 -0700" Date: Wed, 30 May 2001 10:23:54 -0400 Message-ID: <21545.991232634@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/329 X-Sequence-Number: 3170 "tjk@tksoft.com" writes: > If upper() and lower() operate on characters in 8859-1 and other character > sets when the appropriate locale is set, then a difference in the behavior > of upper() and lower() would seem like a bug. Au contraire ... upper() and lower() are not symmetric operations in quite a few non-English locales. I'll let those who regularly work with them give specific details, but handling of accents, German esstet (sp?), etc are the gotchas that I recall. regards, tom lane