This page refers to the
case_sensitive
parameter that is part of a dimension or filter.
case_sensitive
can also be used as part of a model, described on thecase_sensitive
(for models) parameter documentation page.
case_sensitive
can also be used as part of an Explore, described on thecase_sensitive
(for Explores) parameter documentation page.
Usage
dimension: field_name {
case_sensitive: no
}
}
Hierarchycase_sensitive |
Possible Field TypesDimension, FilterAcceptsA Boolean (yes or no) |
Definition
When a dimension
or filter
field is used as a filter, you can change its case-sensitivity by using the case_sensitive
parameter. The case_sensitive
parameter works with most dialects, although some dialects do not have the necessary SQL functions.
By default, case_sensitivity
is on and filters are case-sensitive. However, some dialects do not support this parameter, as described in the case_sensitive
is not supported by some SQL dialects section on this page.
Examples
Stop filters on the name
dimension from being case-sensitive:
Common challenges
case_sensitive
is not supported by some SQL dialects
By default, 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.
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 22.6: