searches are case sensitive

this looks like views wasn’t handling the case where a query that had been processed but still contained strings that db_query uses for arg substitution where passed to db_query. this led to unintended substitutions.

for example, views would pass this sql:

SELECT node.nid FROM node node  WHERE (UPPER(node.title) LIKE UPPER('%s is not the substitution you were looking for%')) AND (node.type IN ('droids')) AND (node.status = '1')   LIMIT 0, 12

to db_query, and the '%s' would get replaced with the first element of $args, which if that happened to be node.title, mysql would see:

SELECT node.nid FROM node node  WHERE (UPPER(node.title) LIKE UPPER('node.title is not the substitution you were looking for%')) AND (node.type IN ('droids')) AND (node.status = ‘1’)   LIMIT 0, 12

looks like case sensitive, but isn’t.

a possible fix just converts '%(s|d|f|b)' --> '%%(s|d|b|f)' before the query is passed to db_query by views like this in views_build_view:

$query = preg_replace('/(%(s|d|b|f))/', '%%$2', $query);

Automatically closed -- issue fixed for two weeks with no activity.