User Guide Getting Started Help Center Documentation Community Training
New LookML
Old LookML
New LookML
  
English
日本語
case_sensitive (for Fields)

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 this documentation page.

case_sensitive can also be used as part of an Explore, described on this documentation page.

Usage

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

Hierarchy

case_sensitive

Possible Field Types

Dimension, Filter

Accepts

A Boolean (yes or no)

Definition

When 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 below.

Examples

Stop filters on the name 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 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:

Top