sfirke commented on issue #26361: URL: https://github.com/apache/superset/issues/26361#issuecomment-1870592714
Hello, sorry you are having this difficulty. This is not a bug in Superset, this is happening between SQLAlchemy (which Superset uses to read data) and your Oracle DB. The proper fixes include upgrading to a version of Oracle that supports Geo JSON, or using a different DB type that does. If those are not options, you could try to hack together a workaround. This is not a Superset-specific issue so I'm going to close it. Feel free to try searching the Superset Slack chat to see if anyone has discussed this topic, otherwise I expect Oracle forums or that community would be the best bet. Or possibly search to see if anyone has a way to do this via SQLAlchemy modification. Good luck! -- 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]
