This page refers to the
case_sensitiveparameter that is part of a model.
case_sensitivecan also be used as part of an Explore, described on this documentation page.
case_sensitivecan also be used as part of a dimension or filter field as described on this documentation page
AcceptsA Boolean (
case_sensitive determines whether filters will be treated as case-sensitive for a given model. All filters related to the model are impacted, including those added in the Explore UI, the Dashboard UI, a filter field, or a measure’s
case_sensitive works by adjusting the
WHERE clause of the SQL that Looker generates. When
case_sensitive: yes, filters are expressed with
LIKE, such as:
case_sensitive: no, filters are expressed with
ILIKE (or equivalent), such as:
Most SQL dialects support
case_sensitive. However, 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. Dialect support is listed below.
Make all filters case-sensitive for a model:
Make all filters not case-sensitive for a model:
case_sensitive Is Not Supported by Some SQL Dialects
For Looker to support
case_sensitive in your Looker project, your database dialect must also support it. The following table shows which dialects support
case_sensitive in Looker 21.0:
DataVirtuality provides a semantic data layer connecting to various database dialects. If Looker supports
case_sensitive for the underlying dialects, then Looker supports
case_sensitive for DataVirtuality connecting to those dialects.
Things to Know
You Can Create a Case-Sensitive Search in MySQL
It is possible to create a case-sensitive search in MySQL without using 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: