How the in-memory filters treat an unset field (null or undefined, or
whatever the comparer turns into null):
"javascript": an unset value is a value like any other, so it differs
from every set value: notEqual, notIn and notContains with a set
value match it;
"sql": an unset value is unknown, as in SQL (Postgres, PostgREST): it
matches only equal / equalInsensitive with null and in with a
list holding null, never notEqual, notIn nor notContains.
Both agree on every other operator: the ordered ones (greaterThan,
range, ...) and the string ones (contains, startsWith, ...) never
match an unset value. Sorting is not affected.
How the in-memory filters treat an unset field (
nullorundefined, or whatever the comparer turns intonull):"javascript": an unset value is a value like any other, so it differs from every set value:notEqual,notInandnotContainswith a set value match it;"sql": an unset value is unknown, as in SQL (Postgres, PostgREST): it matches onlyequal/equalInsensitivewithnullandinwith a list holdingnull, nevernotEqual,notInnornotContains.Both agree on every other operator: the ordered ones (
greaterThan,range, ...) and the string ones (contains,startsWith, ...) never match an unset value. Sorting is not affected.