-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for SQLAlchemy 2.0 #477
Comments
soininen
added a commit
to spine-tools/spine-items
that referenced
this issue
Feb 7, 2025
soininen
added a commit
to spine-tools/Spine-Toolbox
that referenced
this issue
Feb 7, 2025
soininen
added a commit
that referenced
this issue
Feb 7, 2025
soininen
added a commit
that referenced
this issue
Feb 7, 2025
soininen
added a commit
that referenced
this issue
Feb 7, 2025
soininen
added a commit
that referenced
this issue
Feb 7, 2025
soininen
added a commit
that referenced
this issue
Feb 10, 2025
This forces SQLAlchemy engines to accept SQLAlchemy 2.0 style calls only. Re #477
soininen
added a commit
that referenced
this issue
Feb 10, 2025
This should be the last step on our way to SQLAlchemy 2.0 compatibility. Re #477
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It should be relatively easy to migrate to SQLAlchemy 2.0 since we are now on 1.4 which is designated as a "stepping stone" for 2.0. Rough plan, hoping no major restructuring or roadblocks arise:
SQLALCHEMY_WARN_20=1
environment variable as instructed in the link aboveThe text was updated successfully, but these errors were encountered: