dosubot[bot] commented on issue #30612: URL: https://github.com/apache/superset/issues/30612#issuecomment-2414556829
<!-- Greeting --> Hey @rparsonsbb, I'm here to help you with any bugs, questions, and even guide you to become a contributor. Let's squash those bugs together! 😊 <!-- Answer --> The issue you're encountering with the `uniqueidentifier` type in SQL Server when using Superset's meta database likely stems from the lack of specific handling for this data type within Superset's current implementation. As of now, there isn't a documented custom class or type mapping in Superset specifically for handling SQL Server's `uniqueidentifier` type <sup>[[1]](https://github.com/apache/superset/blob/master/superset/db_engine_specs/mssql.py)</sup>. To address this, you might consider extending or customizing the data type handling in Superset's meta database. This could involve creating a custom type mapping or conversion function for the `uniqueidentifier` type. You can look into the `MssqlEngineSpec` class, which handles SQL Server-specific data types, as a starting point for implementing this functionality <sup>[[1]](https://github.com/apache/superset/blob/master/superset/db_engine_specs/mssql.py)</sup>. If you decide to proceed with a pull request, it would be beneficial to add a custom type mapping for `uniqueidentifier` in a similar manner to how other SQL Server types are handled. This could involve defining a new SQLAlchemy type or conversion logic that correctly interprets `uniqueidentifier` values when querying through the meta database. <!-- 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]
