[Bug]: Data Table search returns no results when there should be some

[rmxrmx]

Describe the bug

The search functionality returns no results if anything is typed in, even in cases where an exact match of one cell is used.
Base table:

Searching for exact match in one column:

Searching for exact match in another column:

Typing in anything at all:

Steps to Reproduce

You can download the database I use here. Note that this data was ingested from the Lithuanian Parliament and is licensed CC BY 4.0. Alternatively you can try constructing a similar dataset to the images above.

The actual table code is very basic:

```sql balsavimai
select *
from main_db.bals_individ
where seimo_narys = '${inputs.seimo_nario_vardas.value}'
order by abalsavimo_laikas desc```

<DataTable data={balsavimai} rows=15 search=true>
  <Column id=akaip_balsavo title="Balsas" contentType=colorscale/>
  <Column id=klausimu_grupes title="Klausimas" wrap=true/>
  <Column id=abalsavimo_laikas title="Data"/>
</DataTable>

Logs

No relevant logs I could find.

System Info

System:
OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
Memory: 4.78 GB / 7.67 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm
npmPackages:
@evidence-dev/bigquery: ^2.0.7 => 2.0.8
@evidence-dev/core-components: ^4.8.10 => 4.8.10
@evidence-dev/csv: ^1.0.12 => 1.0.12
@evidence-dev/databricks: ^1.0.7 => 1.0.7
@evidence-dev/duckdb: ^1.0.11 => 1.0.11
@evidence-dev/evidence: ^39.1.13 => 39.1.13
@evidence-dev/motherduck: ^1.0.2 => 1.0.2
@evidence-dev/mssql: ^1.0.9 => 1.1.0
@evidence-dev/mysql: ^1.1.3 => 1.1.3
@evidence-dev/postgres: ^1.0.6 => 1.0.6
@evidence-dev/snowflake: ^1.1.1 => 1.2.0
@evidence-dev/sqlite: ^2.0.6 => 2.0.6
@evidence-dev/trino: ^1.0.8 => 1.0.8

Severity

serious, but I can work around it

Additional Information, or Workarounds

No response

[rmxrmx]

As an update, I added two more columns and the search started to work:

[jediwarpraptor]

What I've found is that this is related to adding a search to a DataTable that does any kind of ${inputs...} filtering. If you comment out any filter references in the base query, suddenly the Search starts working correctly, so almost certainly related to filters.