Skip to content
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

Update to SQLAlchemy 2.0 #322

Open
martinburchell opened this issue Oct 19, 2023 · 2 comments · May be fixed by #385
Open

Update to SQLAlchemy 2.0 #322

martinburchell opened this issue Oct 19, 2023 · 2 comments · May be fixed by #385
Assignees

Comments

@martinburchell
Copy link
Collaborator

SQLAlchemy 1.4 is marked as legacy and at the time of writing is still being maintained. I can't see any mention of an end-of-life date. So this is low priority for now.

My understanding is that SQLAlchemy 2.0 has a more simplified API to earlier versions, meaning there are fewer ways to achieve the same end and leading to more consistent code.

So we should work towards migrating to 2.0. Fortunately this need not be done all at once. See https://docs.sqlalchemy.org/en/14/changelog/migration_20.html

@martinburchell martinburchell self-assigned this Jan 16, 2025
@martinburchell
Copy link
Collaborator Author

@RudolfCardinal I'm going to start work on this unless you've already done so.

@RudolfCardinal
Copy link
Collaborator

Thanks! No, haven't done this yet. Some comments on the CRATE process at https://github.com/ucam-department-of-psychiatry/crate/blob/sqlalchemy2/devnotes/2025_01_sqlalchemy2_databricks/notes_sqlalchemy2.txt

@martinburchell martinburchell linked a pull request Jan 31, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants