Bug description

Since v4.1 (tested against v4.1.2/4.1.4), SQL Lab fails to "SELECT * WHERE" with "Database error: Not acceptable". "SELECT *" query works but any correct "WHERE" clause breaks the query. The same queries against the same DBs work fine with v4.0.1. Superset was deployed from the official helm charts:

• helm 0.14.3: app v4.1.2 (default) / 4.1.4 (custom)
• helm 0.12.11: app v4.0.1

This was observed against MySQL and PostgresSQL DBs. For PostgreSQL, SQL Lab also highlights correct "SELECT * WHERE" queries with warning "The server failed to validate your query”.

Logs:

<IP> - - [05/Nov/2025:12:09:47 +0000] "POST /api/v1/sqllab/execute/ HTTP/1.1" 202 406 "https://<domain>/sqllab/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36"
<IP> - - [05/Nov/2025:12:09:47 +0000] "GET /api/v1/query/updated_since?q=(last_updated_ms:1762344544751) HTTP/1.1" 200 1072 "https://<domain>/sqllab/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36"
2025-11-05 12:09:47,464:INFO:superset.sqllab.sql_json_executer:Query 9202: Running query on a Celery worker
2025-11-05 12:09:47,437:INFO:superset.commands.sql_lab.execute:Triggering query_id: 9202

Screenshots/recordings

No response

Superset version

4.1.3

Python version

3.10

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.