Case insenstive matching

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.

Hi Anya,

We do support the ilike operator for this use case, as listed in this table here :smile:

2 Likes

Amazing, I don’t know how I missed that, thank you!