Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKFpZ-0005Rj-2Y for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2013 22:57:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VKFpY-0007ZG-HQ for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2013 22:57:44 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKFpX-0007Z7-0U for pgsql-general@postgresql.org; Thu, 12 Sep 2013 22:57:43 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKFpO-0006Gd-Fk for pgsql-general@postgresql.org; Thu, 12 Sep 2013 22:57:41 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VKFpO-0007Yy-17 for pgsql-general@postgresql.org; Thu, 12 Sep 2013 15:57:34 -0700 Date: Thu, 12 Sep 2013 15:57:34 -0700 (PDT) From: David Johnston To: pgsql-general@postgresql.org Message-ID: <1379026654020-5770653.post@n5.nabble.com> In-Reply-To: References: Subject: Re: problem with query MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 3.7 (+++) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org Roberto Scattini wrote > what makes the '=C3=B1' char special that makes the queries the same when= it is > not there? My knowledge here is a little rough around the edges but the following is conceptually true: For the most part legacy encodings (or non-encodings as this case technically falls under) recognize only the explicit case-conversions for the latin alphabet A-Z (mapped onto "a-z") without any accents. To reasonably process strings/varchars/clobs that contain accented letters it is necessary to use a more modern encoding - such as UTF-8/Unicode - which contains the necessary logic to perform the additional conversions. these should (not going to test it myself at this time) by case-insensitively identical: abcd=C3=ABFGH ABCD=C3=ABfgh since the "a-d, f-h" can be converted between and the one symbol that cannot, "=C3=AB" is the same in both string....so it isn't that the =C3=AB = breaks things but rather that symbol has no upper-case alternative to equivalently match against...just like numbers and symbols behave in the same situation.= =20 To ASCII =C3=AB is just a symbol without any "letter of alphabet" characteristics. David J. =20 -- View this message in context: http://postgresql.1045698.n5.nabble.com/probl= em-with-query-tp5770637p5770653.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. --=20 Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general