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
In some cases it may be useful to apply a filter based on array content. These would really be new filter operators that would be applicable only to list/array items
Note: these would be the DuckDB builtins to use.
As filter options these would be available in addition to the current options.
(Maybe consider removing the LIKE style operators for lists?)
Both these functions could be negated as well, adding up to 4 new filter operators:
List includes (any)
List excludes = ~list includes
List includes all
List excludes = ~list includes all.
The UI would have to adapt to make it possible to select array elements.
The query behind the picklist should unnest the array value and present the distinct list of values (array elements).
The user can then pick values as usual, and they would be added to the filter's value list.
When applying these filter items to the query, we would construct array values from the list values and use them as argument to the list_has_all and list_has_any functions.
The text was updated successfully, but these errors were encountered:
In some cases it may be useful to apply a filter based on array content. These would really be new filter operators that would be applicable only to list/array items
list_has_all: https://duckdb.org/docs/sql/functions/list#list_has_alllist-sub-list
list_has_any: https://duckdb.org/docs/sql/functions/list#list_has_anylist1-list2
Note: these would be the DuckDB builtins to use.
As filter options these would be available in addition to the current options.
(Maybe consider removing the LIKE style operators for lists?)
Both these functions could be negated as well, adding up to 4 new filter operators:
List includes (any)
List excludes = ~list includes
List includes all
List excludes = ~list includes all.
The UI would have to adapt to make it possible to select array elements.
The query behind the picklist should unnest the array value and present the distinct list of values (array elements).
The user can then pick values as usual, and they would be added to the filter's value list.
When applying these filter items to the query, we would construct array values from the list values and use them as argument to the list_has_all and list_has_any functions.
The text was updated successfully, but these errors were encountered: