mistercrunch commented on issue #29457: URL: https://github.com/apache/superset/issues/29457#issuecomment-2327485406
I'm curious if the type is `BINARY` or some sort of `STRING` / `TEXT`-type data type. Superset should not try to convert a BINARY-like type as text and fail. I'd say nowadays python >= 3.x all python dbapi drivers (or the database itself at a lower level) should handle the `utf-8` conversion themselves. Like if the database allows for various pre-historic character sets for whatever reason, it should hide that from python. database administrators should be standardizing and kill all older/funky character set support. For old legacy apps / database, it should be easy enough to expose views that force the utf-8 conversion upfront so that tools like Superset don't have to deal with legacy/gibberish from old databases and drivers. -- 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]
