vgvoleg opened a new issue, #31022: URL: https://github.com/apache/superset/issues/31022
### Bug description Hello everyone. I'm working on a new db_engine_spec and I've found it very difficult. Dialect I'm trying to integrate with Superset does not support schemas. AFAIK it is not a "rare" scenario - but it is impossible to create physical dataset using table without selecting some schema (only virtual datasets based on queries are available). What can I do to bypass this issue? If there is a good and easy hack - I'd like to use it! It would be nice if db_engine_spec would have supports_schemas = True field that we could override in our custom spec. SQLAlchemy have this field already https://github.com/sqlalchemy/sqlalchemy/blob/rel_1_4/lib/sqlalchemy/engine/default.py#L72, so probably you can rely on it. ### Screenshots/recordings <img width="305" alt="image" src="https://github.com/user-attachments/assets/e9dedd93-0bbb-43f7-8fde-0e210c693759";> ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] 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]
