{"id":578,"date":"2012-11-30T09:17:30","date_gmt":"2012-11-30T09:17:30","guid":{"rendered":"http:\/\/bar-solutions.com\/weblog\/?p=578"},"modified":"2012-11-30T09:17:30","modified_gmt":"2012-11-30T08:17:30","slug":"","status":"publish","type":"post","link":"https:\/\/blog.bar-solutions.com\/?p=578","title":{"rendered":"Case-Insensitive…"},"content":{"rendered":"

When building your queries you might want to search case-insensitive. We normally use the UPPER() function to accomplish this. This is kind of weird IMHO, because you have to uppercase the value you are looking for. I was wondering why we are not using the LOWER() function. I put this question on Twitter the other day and got a lot of replies right away.<\/p>\n

<\/p>\n

\"fritshoogland's <\/a><\/p>\n

Frits Hoogland<\/b> @fritshoogland <\/p>\n

\n<\/p>\n

@patch72<\/a> AFAIK, old computer systems registered everything in uppercase. I know of old govmt systems. prbly people just kept on doing that.<\/p>\n

That would be a very plausible explanation. We do a lot of things in a special way because we are used to doing it like that.<\/p>\n

\"alexnuijten's <\/p>\n

Alex Nuijten<\/b> @alexnuijten <\/p>\n

\n<\/p>\n

@patch72<\/a> wouldn’t lower() introduce special characters like accents? With upper() this will not happen. @fritshoogland<\/a><\/p>\n

I don’t think this will happen. Using a special character like an accent on a character should keep that accent in both upper and lower case.<\/p>\n

\"jurgen_k's <\/a><\/p>\n

Jurgen Kemmelings<\/b> @jurgen_k <\/p>\n

\n<\/p>\n

@alexnuijten<\/a> @patch72<\/a> ik snap het niet? SQL> select upper(‘h\ufffd\ufffd’) from dual; UPPER —– H\u0554EL <\/p>\n