Closed cc-a closed 4 months ago
The aim is for Continuum 1.4 to be compatible with SQLAlchemy 1.4+, so this is a bug, not a version issue. I'll take a look...
I've fixed that and released as 1.4.1. Unfortunately I've also had to pin to SQLAlchemy < 2.0.22 but I'll look to fix that too.
Note that your code is incompatible with 2.0. If you set future=True
on your engine, you should get this exception:
sqlalchemy.exc.ObjectNotExecutableError: Not an executable object: 'BEGIN'
I assume that's the reason nobody else has hit this.
I recently an issue using sql-continuum==1.4.0 and sql-alchemy==1.4.52. To recreate:
gives:
As noted in the deprecation warning of the output the
Connection.execute
API was updated to remove use of plain strings. The new API seems to be assumed byVersioningManager.track_association_operations
leading to a basic incompatibility with SQLAlchemy<2. At present the specified package dependencies for v1.4.0 does not reflect this and I have had to pin sqlalchemy-continuum to <1.4.0 in my environment as other constraints prevent upgrade to SQLAlchemy. I suggest the SQLAlchemy requirement for v1.4.0 be changed to'SQLAlchemy>=2.0'
.