Open Stack

We started talking about SQLAlchemy 2.0 in Openstack most officially in August 2021:

https://lists.openstack.org/pipermail/openstack-discuss/2021-August/024122.html

Since then, lots of work has been done for SQLAlchemy 2.0 compatibility.  oslo.db master IIUC should be fully free of 2.0 deprecation warnings, this is the topic for that: https://review.opendev.org/q/topic:sqlalchemy-20+repo:openstack/oslo.db  however, sqlalchemy-migrate would need to be fully retired from it which hasn't happened yet.

For downstream projects, the vast majority of SQLAlchemy-related code, which is lots of session.query() calls, should not have to change except to the degree that string-based notation for object attributes is removed in favor of actual attributes, e.g. joinedload("networks") becomes joinedload(Machine.networks).

The SQLAlchemy 2.0 migration process is designed to be gradual and starts with building a 2.0 forwards-compliant application that runs under SQLAlchemy 1.4.  This process is documented at https://docs.sqlalchemy.org/en/20/changelog/migration_20.html#the-1-4-2-0-migration-path .   I think a lot of projects are already through this process and are now trying to run directly on the 2.0 release.   


On Wed, Feb 1, 2023, at 8:02 AM, Thomas Goirand wrote:
> Hi,
> 
> SQLAlchemy 2.0 was released 5 days ago. IMO, we should start drawing a 
> plan to support it for Bobcat, and possibly backport patches for 
> Antelope. Note that I have no clue what his implies. Maybe Mike, you 
> could write about it? Has a lot of things changed?
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230201/e41090df/attachment-0001.htm>