This page refers to thecase_sensitive parameter that is part of adimension orfilter.

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

view: view_name {  dimension: field_name {    case_sensitive: no  }}

Definition

When adimension orfilter field is used as a filter, you can change its case-sensitivity by using thecase_sensitive parameter. Thecase_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 thecase_sensitive is not supported by some SQL dialects section on this page.

Examples

Stop filters on thename dimension from being case-sensitive:

dimension: name {  sql: ${TABLE}.name ;;  case_sensitive: no}

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 thecase_sensitive parameter, case sensitivity will vary according to your database setup, which willusually not be case-sensitive.

For Looker to supportcase_sensitive in your Looker project, your database dialect must also support it. The following table shows which dialects supportcase_sensitive in the latest release of Looker: