Currently, in Datatable (and other components), we can choose which field the search applies to—and that works well for simple use cases ![]()
However, I’d like to suggest a small but powerful improvement:
What if we could define a search operator per field?
Right now, searches appear to rely on a general LIKE operator, which can sometimes return broader results than expected.
Example:
If I have project numbers like:
-
2026059
-
2026079
-
2026089
-
2026099
And I search for “202605”, the results may include:
-
2026059

-
2026079

But ideally, the search should return only values that start with “202605”.
Suggested Enhancement
Allow users to define search behavior per field, such as:
-
Starts with
-
Ends with
-
Contains
-
Exact match
This would:
-
Improve search accuracy
-
Reduce confusion for end users
-
Provide more control without needing workarounds
Tadabase has always been great at listening to its community and building intuitive, user-friendly features ![]()
This small enhancement could make a big difference across many apps.
Would love to hear others’ thoughts on this!
