IgnoreCase in WAQL Queries: impossible when using RegEx/Regular Expressions? Will anything I post here ever be answered?

Question

It appears that the only way to do a complex search including one or more strings that I want to NEGATE (i.e. results will NOT contain the strings) is to write a WAQL query using RegEx.

However, due to the strict character limit for WAQL queries in the Query Editor, and by being forced to enter each string as case-insensitive via the RegEx syntax (e.g. to match BAR, Bar, or baR, the RegEx must be written as [bB][aA][rR]), the process of writing an effective query is often tedious, the length/step count/execution time of the expression is typically inefficient, and sometimes, it's impossible to write a query that functions as intended and/or returns the desired result.

Is there any way to add the RegexOptions.IgnoreCase option (either inline in the query, or in a config file somewhere) to make RegEx strings in a WAQL query be handled as case-insensitive?

If not, I sincerely hope that this option/preference will be added in the very near future.

And hopefully, after 3 posts here without a single reply, I'll finally get a response this time, and be able to feel like asking questions in this forum isn't just a complete waste of time.

---

Wwise 2021.1.8
Windows 10 Pro (10.0.19043 Build 19043)
UnrealEditor 5.0.2.0

Answer 1

Thanks for the suggestion. We noted.

Also note the : operator allow for case-insensitive word match.

example:
$ where name : "bar"

will match:
"BIG BAR"
"bar"
"Bar"
"small bar blue"
"CROW_BAR"

Comments

Unfortunately, this method doesn't allow for any other useful Regular Expression functionality. Therefore, while it may be useful in matching a simple string within a property/reference name, it cannot do more complex matching functionality that can be achieved with current standard ECMAScript RegEx, such as:

$ where name=/\b(bar)\b/i
or
$ where name=/\b(?i:bar)\b/

either of these would match "bar", "Bar", or "BAR", but would not match "barrier", "Barn", "embarassed", or "FUBAR".

Furthermore, the WAQL Reference documentation states "ECMAScript regular expressions are used". This is inaccurate as modern ECMAScript allows for several modifiers by default (using the syntax in my examples above) including global (g), multiline (m), and ignoreCase (i). The documentation should be updated to include the differences between the standard ECMAScript RegEx, and the modified version of it that is used in Wwise.

Or, even better yet, Wwise should be updated to support the use of these modifiers, primarily the ignoreCase modifier.