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 no similar issues or pull requests for this yet.
Is your feature related to a problem? Please describe.
I can specify columns to search against, using column_sortable_list. But afaik, it always searches in all columns, which is often unnecessary costly.
Describe the solution you would like.
I would like to be able to pass search terms as keywords eg. "field1 = 'abc'", so that it's the only filter executed on the database level, rather than "field1 = 'abc', field2 = 'abc'".
Describe alternatives you considered
Even better, the filters could be able to differentiate column type and pick more optimal operator than ilike for columns like int or primary key and leverage their indicies. Maybe even between operators for numbers and timestamps?
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Is your feature related to a problem? Please describe.
I can specify columns to search against, using
column_sortable_list
. But afaik, it always searches in all columns, which is often unnecessary costly.Describe the solution you would like.
I would like to be able to pass search terms as keywords eg. "field1 = 'abc'", so that it's the only filter executed on the database level, rather than "field1 = 'abc', field2 = 'abc'".
Describe alternatives you considered
Even better, the filters could be able to differentiate column type and pick more optimal operator than
ilike
for columns like int or primary key and leverage their indicies. Maybe evenbetween
operators for numbers and timestamps?Additional context
No response
The text was updated successfully, but these errors were encountered: