# Case insenstive matching
**URL:** https://community.holistics.io/t/case-insenstive-matching/2116
**Category:** Ask the Community
**Tags:** aql
**Created:** [September 26, 2024, 4:52pm UTC](https://community.holistics.io/t/case-insenstive-matching/2116 "2024-09-26T16:52:24Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@anya.conti](https://community.holistics.io/u/anya.conti)
#### Post date: [September 26, 2024, 4:52pm UTC](https://community.holistics.io/t/case-insenstive-matching/2116/1 "2024-09-26T16:52:24Z")
Is there any way to do case insensitive matching in AQL? We’re not finding any lower / upper functions that would help us with this, but might be missing something.
ex. if we have values of “dandelion”, “DANDELION”, and “Dandelion” in a table, then in SQL we could do UPPER(field) == ‘DANDELION’ and it would match to all 3. However, we can’t use SQL in ad hoc dimensions or to reference an AQL field.
In AQL, we’ve so far resorted to listing all existing case variations which is a little cumbersome and could end up not catching other variations in the future. For example, if we start with “book” and “BOOK” and explicitly define those 2, but then “Book” appears later, it wouldn’t be included.
---
### Author:  [@tan](https://community.holistics.io/u/tan)
#### Post date: [September 26, 2024, 4:58pm UTC](https://community.holistics.io/t/case-insenstive-matching/2116/2 "2024-09-26T16:58:14Z")
Hi Anya,
We do support the `ilike` operator for this use case, as listed in this table here 😄
> **[AQL Operators | Holistics Docs (4.0)](https://docs.holistics.io/as-code/reference/operator#text)**
>
> A key component of AQL's query syntax involves the utilization of operators to generate more precise metrics.
---
### Author:  [@anya.conti](https://community.holistics.io/u/anya.conti)
#### Post date: [September 26, 2024, 4:59pm UTC](https://community.holistics.io/t/case-insenstive-matching/2116/3 "2024-09-26T16:59:31Z")
Amazing, I don’t know how I missed that, thank you!