Roberto Scattini wrote > what makes the 'ñ' 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ëFGH ABCDëfgh since the "a-d, f-h" can be converted between and the one symbol that cannot, "ë" is the same in both string....so it isn't that the ë 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. To ASCII ë is just a symbol without any "letter of alphabet" characteristics. David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/problem-with-query-tp5770637p5770653.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
