You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sqlalchemy is currently pinned to version 1.4.27 because upgrading past 1.4.27 results in warnings which cause test errors, e.g.:
SAWarning: Dialect mssql:pymssql will not make use of SQL compilation caching as it does not set the 'supports_statement_cache' attribute to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Dialect maintainers should seek to set this attribute to True after appropriate development and testing for SQLAlchemy 1.4 caching support. Alternatively, this attribute may be set to False which will disable this warning.
All our engine dialects inherit from base classes that include supports_statement_cache = True, but as of v1.4.28 (not 1.4.5 as it says in the docs), sqlalchemy requires third party dialects to explicitly declare that too.
sqlalchemy is currently pinned to version 1.4.27 because upgrading past 1.4.27 results in warnings which cause test errors, e.g.:
SAWarning: Dialect mssql:pymssql will not make use of SQL compilation caching as it does not set the 'supports_statement_cache' attribute to
True
. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Dialect maintainers should seek to set this attribute to True after appropriate development and testing for SQLAlchemy 1.4 caching support. Alternatively, this attribute may be set to False which will disable this warning.All our engine dialects inherit from base classes that include
supports_statement_cache = True
, but as of v1.4.28 (not 1.4.5 as it says in the docs), sqlalchemy requires third party dialects to explicitly declare that too.We should be able to fix this by just adding
supports_statement_cache = True
to each dialectThe text was updated successfully, but these errors were encountered: