This page refers to the
case_sensitiveparameter that is part of an Explore.
case_sensitivecan also be used as part of a model, described on this documentation page.
case_sensitivecan also be used as part of a dimension, described on this documentation page.
AcceptsA Boolean (
case_sensitive determines whether or not filters will be treated as case sensitive on a given Explore. All filters related to the Explore are impacted, including those added in the Explore UI, Dashboard UI, and
case_sensitivity is on and filters are case sensitive. However, some dialects do not support this parameter, as described below.
case_sensitive works by adjusting the
WHERE clause of the SQL that Looker generates. When
case_sensitive is on, filters are expressed with
LIKE, such as:
case_sensitive is off, filters are expressed with
ILIKE (or equivalent), such as:
Make all filters case sensitive for the Product Explore
Make all filters not case sensitive for the Customer Explore
case_sensitive Is Not Supported By Some SQL Dialects
case_sensitivity is on and filters are case sensitive. If your SQL dialect doesn’t support the
case_sensitive parameter, case sensitivity will vary according to your database setup, which will usually not be case sensitive.
Looker’s ability to provide
case_sensitive depends on the database dialect’s ability to support this functionality. The list below shows which dialects support
case_sensitive functionality in the most recent Looker release:
Things to Know
You Can Create a Case-Sensitive Search in MySQL
It is possible to create a case-sensitive search in MySQL, even though it does not support the
case_sensitive parameter. In MySQL certain data types, called binary strings, store text as a series of numbers. The capitalization of the text makes a difference in the numbers that are used. Therefore, if you convert your text to a binary string, you can make searches that are case sensitive. For example: