AutoTable loses computed fields on search
8 Replies
Hello,
I believe that this happens because of the separate databases that filters and searchs are run on. Computed fields aren't added to the search database (Elasticsearch) because they're computed on read time.
What would you expect to see when searching?
hm I didn't realize there was a different database involved in search. I thought it was just filtering the model.
can you confirm that's definitely the case? Is there a way to use autotable such that it only uses model filters and doesn't use the search database?
If you want to do that you need to turn searchable off and build your own search but that might not work with auto table
Actually, it would cause you can insert filters. The searchbar would be separate and the searching would need to be done on particular columns that you select using the startsWith filter
cool i'll check that out
Not that startsWith is an exact match so you might want to have a lowercase version of the string fields and lowercase all search inputs
yeah I'd seen that
so filter would let me pass in specific filters in code but what about UI for filtering?
What do you mean by UI for filtering? I thought you wanted to have a search. If you want additional filters you can add something and pass it to the filter object. It would then rerender/fetch data in the table
Is that what you meant?