clach04 commented on issue #30734: URL: https://github.com/apache/superset/issues/30734#issuecomment-2442776794
As reported I **think** this is a manifestation of a bug in the (latest, as of 2024-10-28) Ingres Adapter (which supports SQLAlchemy 2.x and most of 1.x) - see https://github.com/ActianCorp/sqlalchemy-ingres/issues/68 this is NOT a problem with older versions of the Ingres Adapter which have full SQLAlchemy version 1.x support. Either use an older version of the Ingres SQLAlchemy Adapter that fully supports SQA version 1.0 .. or SuperSet needs to be updated to use SQLAlchemy version 2. The trigger for this is the use of SQLAlchemy version 1.x, rather than the 2.x series. I'm note clear how much work it would take to update SuperSet (but I do not think just bumping the version dependency is enough). -- 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]
