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

[WIP] Upgrade SQLAlchemy #5492

Closed
wants to merge 21 commits into from
Closed

Conversation

tmpayton
Copy link
Contributor

Summary (required)

  • Resolves #issue_number

(Include a summary of proposed changes and connect issue below)

Required reviewers

(Include who is required to review prior to merge. For example: One designer and two front end developer reviews are required prior to merge)

Impacted areas of the application

General components of the application that this PR will affect:

Screenshots

(Include a screenshot of the new/updated features in context (“in the wild”). If it is an interface change, include both before and after screenshots)

Related PRs

Related PRs against other branches:

branch PR
fix/other_pr link
feature/other_pr link

How to test

(Include any information that may be helpful to the reviewer(s). This might include links to sample pages to test or any local environmental setup that is unusual such as environment variable (never credentials), API version to point to, etc)

System architecture updates (if applicable)

(If this pull request changes our current system diagram, include a description of those changes here and create a new ticket to update the system diagram)

webservices/sorting.py Outdated Show resolved Hide resolved
@cnlucas
Copy link
Member

cnlucas commented Aug 7, 2023

We are postponing this upgrade because it will require some major re-writing to how we are connecting to the database.

We discovered that we can no longer reset SQLALCHEMY_DATABASE_URI. Engines are now created when calling init_app rather than the first time they are accessed. The current recommended way of getting around this issue is to build an app factory. These changes would require us to re-create the app when we need to reset the connections. This is extremely high risk for us.

Here's a helpful discussion of the issue:
pallets-eco/flask-sqlalchemy#1172

We will be watching and continuing to work on solutions in case this upgrade becomes more urgent.

@cnlucas cnlucas closed this Aug 7, 2023
@cnlucas cnlucas deleted the feature/5486-upgrade-sqlalchemy branch July 22, 2024 15:06
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 this pull request may close these issues.

2 participants