dosubot[bot] commented on issue #30863:
URL: https://github.com/apache/superset/issues/30863#issuecomment-2460710760

   <!-- Greeting -->
   Hello @pferder! I'm here to assist you with any bugs, questions, or 
contributions you may have for Superset. Let's work together to solve this 
issue!
   
   <!-- Answer -->
   Superset's handling of PostgreSQL UUID and PostGIS geometry types can 
sometimes present challenges. For UUIDs, Superset uses the `UUIDType` from 
`sqlalchemy_utils`, which should generally work well with PostgreSQL's UUID 
type 
<sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2020-09-28_17-57_b56500de1855_add_uuid_column_to_import_mixin.py)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/superset/utils/mock_data.py)</sup>.
 However, issues can arise if there are discrepancies in how UUIDs are defined 
or used in your database schema compared to what Superset expects.
   
   Regarding PostGIS geometry types, there isn't specific information available 
in the repository about how Superset handles these types, which might indicate 
a lack of direct support or specific configuration for PostGIS geometries 
<sup>[[3]](https://github.com/apache/superset/blob/master/superset/db_engine_specs/postgres.py)</sup>.
   
   To troubleshoot this issue, you might want to:
   
   1. Ensure that your database schema aligns with the expected types and 
configurations used by Superset.
   2. Check if there are any custom configurations or plugins that might affect 
how these types are handled.
   3. Review the Superset logs for any specific error messages that could 
provide more insight into the problem.
   
   If the issue persists, consider creating a minimal reproducible example and 
checking if there are any recent updates or community discussions that might 
address this problem.
   
   
   <!-- 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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to