Use of wildcards in VAG scripts

[René]

Cavagnaro,

Based on the documentation and release notes the option "filters-allow-wildcards-in-values" was added in version 7.5.

René

[cavagnaro]

I believe that was launched in order to restrict the use of wildcards on filters, not to implement them as they were available. Maybe some data containing * and don't using it as a filter was the problem and fixed  with this option.

From statserver 7.0 users guide:

Use the wildcard character “*” (asterisk) in place of the value in filter
functions. PairExists(“Key”,”*”) would return 1 for true if any key-value
pair exists where the key equals “Key”, regardless of the value of that pair.

[cavagnaro]

Oh ok my bad, you were talking more about the statserver option not the wildcard feature itself.
Sorry

[Kevin S]

According to the description, the wildcard option was previously available, but it matched ANY instance.

This option permits you to get narrow it down to a subset.
For example, in the original posting, Mark was looking to use for any skillset starting with "IFA_".
Prior to 7.5, using PairExists("MySkill", "*") would give you any existence of MySkill. If it was used as part of a string - for example, PairExists("Password", "A*terisk") - it would take the * as a literal character within the string and not as a wildcard.

Post-7.5, you could do PairExists("MySkill", "IFA_*") to match anything starting with "IFA_", but it would not match the KVP (MySkill, "XYZ") because XYZ does not start with "IFA_"

Disclaimer: I have not tested the various permutations of what works and what doesn't - such as, would "A*terisk" match "Asterisk", "Abbterisk", "A12345terisk", etc. This is left as an exercise for the student.