You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are use cases where entity views contain a list of strings as a comma separated string (also see #104 ). What kind of filter or sorting can we support for such attributes? The currently implemented attribute filters only support scalar values.
The common filters for a collection are with one of the following quantifiers
at least one element in the collection must match the filter criterion
at least one element in the collection must match one of the filter criteria
all elements in the collection must match the filter criterion
no element may match the filter criterion
Examples
Give me all documents that have a partner whos' name starts with 'Rupp'
Give me all documents that have a partner whos' name either starts with 'Rupp' or starts with 'Kleider'
Give me all documents where every partner's name starts with 'Rupp'
Give me all documents that have no partner whos' name starts with 'Rupp'
I don't think there are any common sorting criteria one could apply for such collections.
A possible solution to the bad default problem could be to disallow applying regular filters on attributes within collections and instead force to use a dedicated EntityViewSetting API which makes the choice of "filtering the collection to a subset" vs "finding elements where the collection matches a criteria" explicit. This is required for #1498
The text was updated successfully, but these errors were encountered:
There are use cases where entity views contain a list of strings as a comma separated string (also see #104 ). What kind of filter or sorting can we support for such attributes? The currently implemented attribute filters only support scalar values.
The common filters for a collection are with one of the following quantifiers
Examples
I don't think there are any common sorting criteria one could apply for such collections.
A possible solution to the bad default problem could be to disallow applying regular filters on attributes within collections and instead force to use a dedicated
EntityViewSetting
API which makes the choice of "filtering the collection to a subset" vs "finding elements where the collection matches a criteria" explicit. This is required for #1498The text was updated successfully, but these errors were encountered: