Enumeration ObjectFilterOperator

If the first operand is not less than or equal to the second operand, those two arguments are automatically swapped. For string comparison, a default lexical ordering is used. Note: Do not compare a number with a string, as the result is not defined.

Primitive value types (number, string, boolean, null) contain only the identical value. Object properties match if all the key-value pairs of the specified object are contained in them. Array properties match if all the specified array elements are contained in them.

The general principle is that the contained object must match the containing object as to structure and data contents recursively on all levels, possibly after discarding some non-matching array elements or object key/value pairs from the containing object. But remember that the order of array elements is not significant when doing a containment match, and duplicate array elements are effectively considered only once.

As a special exception to the general principle that the structures must match, an array on toplevel may contain a primitive value:

Contains([1, 2, 3], [3]) => true
Contains([1, 2, 3], 3) => true

Note: do not check for undefined value as it is converted to null implicitely by JSON. Use the NotExists operator instead.

Note: Do not compare a number with a string, as the result is not defined.

Note: Do not compare a number with a string, as the result is not defined.

For example:

In(47, [1, 46, 47, "foo"]) => true
In(47, [1, 46, "47", "foo"]) => false
In({ "foo": 47 }, [1, 46, { "foo": 47 }, "foo"]) => true
In({ "foo": 47 }, [1, 46, { "foo": 47, "bar": 42 }, "foo"]) => false

For string comparison, a default lexical ordering is used. Note: Do not compare a number with a string, as the result is not defined.

For string comparison, a default lexical ordering is used. Note: Do not compare a number with a string, as the result is not defined.

If pattern does not contain percent signs or underscores, then the pattern only represents the string itself; in that case LIKE acts like the equals operator (but less performant). An underscore (_) in pattern stands for (matches) any single character; a percent sign (%) matches any sequence of zero or more characters.

LIKE pattern matching always covers the entire string. Therefore, if it's desired to match a sequence anywhere within a string, the pattern must start and end with a percent sign.

To match a literal underscore or percent sign without matching other characters, the respective character in pattern must be preceded by the escape character. The default escape character is the backslash. To match the escape character itself, write two escape characters.

For example, the pattern string %a_c\\d\_ matches abc\d_ in hello abc\d_ and acc\d_ in acc\d_, but nothing in hello abc\d_world. Note that in programming languages like JavaScript, Java, or C#, where the backslash character is used as escape character for certain special characters you have to double backslashes in literal string constants. Thus, for the example above the pattern string literal would look like "%a_c\\\\d\\_".

If the first operand is not less than or equal to the second operand, those two arguments are automatically swapped. For string comparison, a default lexical ordering is used. Note: Do not compare a number with a string, as the result is not defined.

Primitive value types (number, string, boolean, null) contain only the identical value. Object properties match if all the key-value pairs of the specified object are not contained in them. Array properties match if all the specified array elements are not contained in them.

The general principle is that the contained object must match the containing object as to structure and data contents recursively on all levels, possibly after discarding some non-matching array elements or object key/value pairs from the containing object. But remember that the order of array elements is not significant when doing a containment match, and duplicate array elements are effectively considered only once.

As a special exception to the general principle that the structures must match, an array on toplevel may contain a primitive value:

NotContains([1, 2, 3], [4]) => true
NotContains([1, 2, 3], 4) => true

Note: do not check for undefined value as it is converted to null implicitely by JSON. Use the Exists operator instead.

For example:

NotIn(47, [1, 46, 47, "foo"]) => false
NotIn(47, [1, 46, "47", "foo"]) => true
NotIn({ "foo": 47 }, [1, 46, { "foo": 47 }, "foo"]) => false
NotIn({ "foo": 47 }, [1, 46, { "foo": 47, "bar": 42 }, "foo"]) => true