dosubot[bot] commented on issue #35348: URL: https://github.com/apache/superset/issues/35348#issuecomment-3353962675
<!-- Greeting --> Hi @M11VCS! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Superset does not change the case of schema names—it displays them exactly as provided by the SQLAlchemy-ibmi driver. The reason you see lowercase schema names is that SQLAlchemy (and many database drivers) return unquoted identifiers in lowercase, unless the schema name contains special characters or is explicitly quoted, in which case the original case is preserved. This is standard SQLAlchemy behavior and not specific to Superset. Schemas with special characters (like £ or §) are returned as-is, which is why those appear in uppercase and work as expected. There is no Superset configuration to force all schema names to uppercase. If you need all schemas to appear in uppercase, you would need to look for a setting or patch in the SQLAlchemy-ibmi dialect or the IBM i driver to control identifier case, or possibly override the engine spec in Superset to transform schema names to uppercase before display, though this is not the default behavior and would require custom code. For now, manually specifying schema names in uppercase when creating datasets may help as a workaround. For reference, Superset's schema listing logic simply passes through whatever the driver returns, without modifying the case of schema names [(source)](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/db_engine_specs/base.py). Similar case sensitivity issues have been seen with other engines like PostgreSQL and Snowflake, and the root cause is always in the driver or dialect, not in Superset itself [(source)](https://github.com/apache/superset/issues/32564). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/31a6cbe8-142d-4ad1-9f06-8053abe0d12a?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35348) -- 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]
