case_sensitive

LookML
Version

On this Page
Docs Menu

Go to Explore Parameter List

This page refers to the case_sensitive parameter that is part of an explore

case_sensitive can also be used as part of a model, described here

case_sensitive can also be used as part of a dimension, described here

Usage

case_sensitive is a child of
explore
explore: view_name
...
1st
Tab
case_sensitive: true
a boolean
true
false

Definition

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 filters parameter.

By default, 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 = or LIKE, such as:

WHERE name = 'bob' WHERE name LIKE '%bob%'

When case_sensitive is off, filters are expressed with ILIKE (or equivalent), such as:

WHERE name ILIKE 'bob'

Examples

Make all filters case sensitive for the product explore

- explore: product case_sensitive: true

Make all filters not case sensitive for the customer explore

- explore: customer case_sensitive: false

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 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:

- dimension: will_NOT_be_case_sensitive sql: ${TABLE}.something   - dimension: will_be_case_sensitive sql: CAST(${TABLE}.something AS BINARY)

Still have questions?
Go to Discourse - or - Email Support
Top