Move to SQLAlchemy API 2.0

Bug #1929383 reported by Rodolfo Alonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.db
New
Undecided
Unassigned

Bug Description

Since SQLAlchemy 1.4, this library exposes the API 2.0 [1].

To enable "future" behaviour in the ORM ``Session`` class, ``Session.future`` flag should be set to True.

[1]https://github.com/zzzeek/sqlalchemy/commit/5de0f1cf50cc0170d8ea61304e7b887259ab577b

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.