You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "M11VCS (via GitHub)" <gi...@apache.org> on 2025/09/30 22:10:32 UTC
[I] Case Sensitive Schema Names [superset]
M11VCS opened a new issue, #35348:
URL: https://github.com/apache/superset/issues/35348
### Bug description
Hello,
I'm using SQLAlchemy-ibmi package .
When I create a dataset it fails on schema names which are shown all in lowercase.
All schemas that on IBM I have a special character , like £ or § , then the schema is shown uppercase and everything in superset works fine.
Schema in IBM I are all UPPERCASE by definition, so I do not understand why in Superset are treated in lowercase.
Is it a workaround to list all schema in UPPERCASE so I can proceed with my development.
Thank you for your support.
<img width="130" height="317" alt="Image" src="https://github.com/user-attachments/assets/916e1025-2461-468d-8254-9221d69e95d0" />
<img width="679" height="84" alt="Image" src="https://github.com/user-attachments/assets/91ed5e00-9f8d-4daa-9791-a4635f665434" />
### 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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #35348:
URL: https://github.com/apache/superset/issues/35348#issuecomment-3544311295
Did that last answer suffice @M11VCS ? Not sure how to proceed with this, since I don't use that DB and haven't run into this as a problem.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "M11VCS (via GitHub)" <gi...@apache.org>.
M11VCS commented on issue #35348:
URL: https://github.com/apache/superset/issues/35348#issuecomment-3353979338
> ***@***.*** , I cannot manually type the schema as it’s selected from dropdown list.
How can I manually type it?
Best regards,
Giovanni Michielin
Victoria Computer Services LTD
The Bradfield Centre
184 Cambridge Science Park Rd
Cambridge
CB4 0GA
United Kingdom
On 1 Oct 2025 at 00:13 +0200, dosubot[bot] ***@***.***>, wrote:
> dosubot[bot] left a comment (apache/superset#35348)
> Hi @M11VCS! I'm Dosu and I’m helping the superset team.
> 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). 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).
> To reply, just mention @dosu.
> How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.Message ID: ***@***.***>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #35348:
URL: https://github.com/apache/superset/issues/35348#issuecomment-3353988932
<!-- Answer -->
Superset's dataset creation UI does not support manual typing of schema names—you can only select from the dropdown list of schemas provided by the backend. The dropdown allows you to search and filter by typing, but you cannot enter a schema name that isn't listed or correct the case manually. This behavior is enforced by the frontend components and there is no configuration or hidden option to enable manual schema entry in the current version of Superset [(source)](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/DatabaseSelector/index.tsx).
If you need to use a schema that isn't appearing correctly, the only workaround would be to address the issue at the database driver or dialect level so the correct schema names are returned to Superset. The UI itself cannot be bypassed for manual schema entry.
<!-- 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/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/614ca7fe-ab92-4464-af18-27b9c6aaeb1a?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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #35348:
URL: https://github.com/apache/superset/issues/35348#issuecomment-4898810762
Closing as not-planned, since it's a driver-specific identifier-case normalization from the sqlalchemy-ibmi dialect (IBM i); Superset displays what the dialect returns. Any fix likely belongs upstream in the dialect.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Case Sensitive Schema Names [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #35348: Case Sensitive Schema Names
URL: https://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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org