Skip to main content

Operators

Following is a list of operators defined by MQL:

Operator name

Symbol

Supported by Filter Types

EQUALS

= <value>

All

EQUALS WITHIN

= <value> WITHIN (search properties)

text, semantic_search_text

NOT EQUALS

!= <value> or <> <value>

Model, category, profile attribute, custom attribute, UDP, system attribute, data profiling attribute, related object property, ExpandedMembersOfRole

EQUALS ANY

= ANY (v1, v2, …, vn)

Model, category, profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, related object property, ExpandedMembersOfRole

NOT EQUALS ANY

!= ANY (v1, v2, …, vn)

Model, category, profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, related object property, ExpandedMembersOfRole

EQUALS ALL

= ALL (v1, v2, …, vn)

profile attribute, custom attribute, UDP, system attribute, "Data Profiling"."Inferred Data Types", related object property, ExpandedMembersOfRole

NOT EQUALS ALL

!= ALL (v1, v2, …, vn)

profile attribute, custom attribute, UDP, system attribute, "Data Profiling"."Inferred Data Types", related object property, ExpandedMembersOfRole

EQUALS WHERE

=WHERE (…)

System attribute Model, "Mentioned Objects" and custom relationship

NOT EQUALS WHERE

!=WHERE (…)

System attribute Model, "Mentioned Objects" and custom relationship

EXISTS

EXISTS

profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, related object property, ExpandedMembersOfRole

NOT EXISTS

NOT EXISTS

profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, related object property, ExpandedMembersOfRole

STARTS WITH

STARTS WITH <value>

profile attribute, custom attribute, UDP, system attribute, related object property

NOT STARTS WITH

NOT STARTS WITH <value>

profile attribute, custom attribute, UDP, system attribute, related object property

ENDS WITH

ENDS WITH <value>

profile attribute, custom attribute, UDP, system attribute, related object property

NOT ENDS WITH

NOT ENDS WITH <value>

profile attribute, custom attribute, UDP, system attribute, related object property

CONTAINS

CONTAINS <value>

profile attribute, custom attribute, UDP, system attribute, related object property

NOT CONTAINS

NOT CONTAINS <value>

profile attribute, custom attribute, UDP, system attribute, related object property

BEFORE

BEFORE <value> (exclusive)

"Created Date", "Updated Date", profile attribute, custom attribute, related object property with a date or datetime data type

AFTER

AFTER <value> (exclusive)

"Created Date", "Updated Date", profile attribute, custom attribute, related object property with a date or datetime data type

BETWEEN

BETWEEN <value> AND <value> (inclusive)

"Created Date", "Updated Date", data profiling attribute, profile attribute, custom attribute, system attribute, related object property with a date, datetime or numeric data type

LESS THAN

< <value>

Data profiling attribute, profiling attribute, custom attribute, system attribute, related object property with a numeric data type

LESS THAN OR EQUAL TO

<= <value>

Data profiling attribute, profiling attribute, custom attribute, system attribute, related object property with a numeric data type

GREATER THAN

> <value>

Data profiling attribute, profiling attribute, custom attribute, system attribute, related object property with a numeric data type

GREATER THAN OR EQUAL TO

>= <value>

Data profiling attribute, profiling attribute, custom attribute, system attribute, related object property with a numeric data type

Note:

When applied to a profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, or a related object property, a filter with the =, !=, <, <=, >, >=, = any (...), != any (...), = all (...), != all (...), [not] starts with, [not] ends with, [not] contains, before, after or between operator would only return any results if the profile attribute, custom attribute, custom relationship, UDP, system attribute, data profiling attribute, or related object property is applicable to the objects and the filter condition is satisfied. NOT EXISTS returns objects that the attribute is not applicable to.

In other words, if an object does not have any attribute Physical Name, any "Physical Name" filter with the operator =, !=, = ANY (...), != ANY (...), = ALL (...), != ALL (...), [NOT] STARTS WITH, [NOT] ENDS WITH, [NOT] CONTAINS, BEFORE, AFTER or BETWEEN will never return this object. But NOT EXISTS will return this object.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!