rusackas commented on PR #42192: URL: https://github.com/apache/superset/pull/42192#issuecomment-5012233801
Found it: pandas 2.3.3 requires SQLAlchemy>=2.0 to take its SQLAlchemy connection path. We're still pinned to 1.4.54, so pandas silently falls back to the raw sqlite3 dtype path and every `to_sql` call with a TypeEngine dtype blows up (`ValueError: col1 (TEXT) not a string`). That's a SQLAlchemy 2.0 migration, not something this bump can fix on its own. -- 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]
