dosubot[bot] commented on issue #31022: URL: https://github.com/apache/superset/issues/31022#issuecomment-2491661163
<!-- Greeting --> Hello @vgvoleg! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's tackle this issue together! <!-- Answer --> To address the issue of creating a dataset without selecting a schema in Superset, you can consider the following approach: 1. **Custom DB Engine Spec**: You can create a custom `db_engine_spec` for your database engine. In this custom spec, you can override methods to handle the absence of schemas. While Superset does not currently have a `supports_schemas` attribute in its `db_engine_spec`, you can implement logic in your custom spec to bypass schema requirements. 2. **Adjust Engine Parameters**: Use the `adjust_engine_params` method in your custom `db_engine_spec` to modify the SQLAlchemy URI and connection arguments. This can help ensure that queries run correctly without requiring a schema. 3. **Modify Frontend Logic**: If you have control over the frontend, you might consider modifying the logic in the `DatabaseSelector` component to handle cases where schemas are not applicable. This could involve conditionally rendering the schema selection UI based on the database engine's capabilities. 4. **SQLAlchemy's `supports_schemas`**: Although Superset does not directly use SQLAlchemy's `supports_schemas` attribute, you can leverage this attribute in your custom spec to determine whether to enforce schema selection. These steps should help you integrate a database engine that does not support schemas into Superset. If you need further customization, you might need to dive deeper into the Superset codebase to adjust how datasets are created and managed. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- 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]
