Actions
Support #7642
closedUpgrade Flask-SQLAlchemy
Start date:
04/13/2023
Due date:
% Done:
0%
Estimated time:
To be discussed:
Description
Flask-SQLAlchemy is currently pinned to <3.0.0, because 3.0.0 removed sessionmaker, which is used in mentat.services.sqlstorage.py. Flask-SQLAlchemy now requires active application context for sessions and engines, so the approach to sessions in sqlstorage.py would have to change.
Another possible solution of this problem is to completely replace Flask-SQLAlchemy with SQLAlchemy (see issue #7545).
SQLAlchemy is also pinned to <2.0.0 because of Flask-SQLAlchemy, so it should also be upgraded in this issue.
Related issues
Actions