Upgrade SQLAlchemy to 1.4.x #6122
jqnatividad
started this conversation in
Ideas
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As there are several modernization issues/initiatives related to SQLAlchemy/Postgres/datastore (#6086, #5953, #5863, #5799, #5796, #5847, #5855, #6104 to mention a few), the team may want to consider upgrading SQLAlchemy from v1.3.5 to v1.4 (Belying the seeming minor version upgrade, SQLAlchemy has made 38 releases since v1.3.5).
As it happens, "SQLAlchemy 1.4 establishes itself as the starting point for the SQLAlchemy 2.0 project, which will move fully to Python 3 only as well as finalize the new APIs introduced in release 1.4.0", echoing CKAN's modernization roadmap.
As 1.4 is being positioned as a migration point/transitional release to SQLAlchemy 2.0, it features a "2.0 Deprecations Mode" that should help with migration.
Migrating to 1.4 also makes CKAN ready for "SQLAlchemy 2.0" which focuses "on making something of a fresh start from over a decade of older architectural patterns, as well as the introduction of native caching support for all SQL constructs and similar features which are essentially "game changer" kinds of changes."
Given the foundational nature of the upgrade, perhaps the initial migration can be limited to the datastore's Postgres backend, where the performance/caching benefits would be most apparent without changing the Datastore API.
Maybe, even create a new postgres backend that is a drop-in replacement for the current one to further isolate changes.
Beta Was this translation helpful? Give feedback.
All reactions