What's the difference between LIKE and MATCHES security rule statements?
It seems to be doing about the same looking at the official definitions below. Maybe I missed something.
Like: http://help.qlik.com/en-US/sense/3.2/Subsystems/ManagementConsole/Content/operator-like.htm
The security rules support the regular expression operator "like". This operator is case insensitive.
Syntax:
(EXPRESSION) like (EXPRESSION)
Examples and results:
| resource.name like "mya*" | Evaluates all resources with names beginning with "mya" to True, irrespective of case. Entering an asterisk at the end of the condition in the Basic view automatically translates to "like" in the condition in the Advanced view. |
Matches: MATCHES ‒ Qlik Sense
The security rules editor supports the regular expression operator "matches". This operator is case insensitive and returns results that match your expression, irrespective of case. Regex start and end anchors are implicitly added.
Syntax:
(EXPRESSION) matches (EXPRESSION)
Examples and results:
| resource.name matches ".*yAp.*" | Evaluates all resources with names containing "yap" to True, irrespective of case. |
| resource.resourcefilter matches "Stream_\\w{8}-\\w{4}-\\w{4}-\\w{4}-\\w{12}" | Evaluates to True if the access request resource filter has the correct format. |
