Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?
SaaS
What do you need help with?
When I start searching using the “magnifier” icon, the search occurs over the row number. It does not perform any full-text-search over the visible fields, regardless of their type.
I have the same problem in application builder. Even if I allow to search over multiple fields, the search actually occurs only over the (invisible) id.
The workaround would be to use browser-level search (Ctrl+F on windows), but… it searches only over the visible fields. I have to scroll (down and right) to another view and only when I am in this particular subspace of the table, the browser-level search actually finds the rows. I suppose this has something to do with how the table is rendered for performance, but if this is the case, the search built into the Baserow must be more functional.
The browser-level search probably does not work, at least not in Chrome, because “the page uses JavaScript to do a virtual DOM where the content outside of the viewport in the page doesn’t actually exist”
So the only remaining question is how to force the embedded search to work properly
Hi @MKPD, let me clarify: when you search for Department manager and that exact text exists in the table, those results appear. But, when searching for Department manager is ... with no exact match, no results show up. Are you asking if we could show fields containing Department manager even when searching for the longer phrase Department manager is ...?
I think I understand where the problem is. The search feature embedded in Baserow works on tables created directly in Baaserow. However, then the table is synced from Postgres, Baserow is missing some indexes and you cannot perform the search?
When I search for Department manager and that exact text exists in the table, those results DO NOT appear. I do not expect any fuzzy, full-text-search logic. I only want exact matches on the phrase I am looking for. The results for exact search do not show up.
I cannot see any documentation on how to use search so I expect it to work without any “query language”, is that correct?
Hi @MKPD, could you please provide a screenshot or video of the issue? I’m unable to reproduce it – when I search for Department manager and that exact text exists in the table, the results show up correctly.
This is correct. They show up correctly in the demo database. However, when the database is a synchronized postgres database, not a pure Baserow table, the search produces no results. I assume this is by design.
I’ve checked this and it seems it’s a bug. When a data sync table is created, full text search indexes aren’t updated. Only if some data change in the source, and then a table is re-synchronized in Baserow, full text search indexes are updated, but only for rows affected.
