mosescha1972 opened a new issue, #37515: URL: https://github.com/apache/superset/issues/37515
### Bug description The error appears to follow this execution flow: Native Filter ↓ Superset Query Context Builder ↓ OracleEngineSpec.apply_limit / apply_orderby ↓ Forced subquery wrapping with ORDER BY ↓ Oracle’s strict GROUP BY validation ↓ ORA-03162 (GROUP BY clause violation) ↓ API returns 400 Bad Request ↓ UI displays “Network error” This issue occurs only with Oracle when applying filters. Other databases work correctly because they are more permissive with GROUP BY behavior, while Oracle enforces strict rules and fails when Superset generates wrapped queries with positional or incompatible GROUP BY clauses. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
