Closed davidism closed 2 years ago
Thanks a lot for the heads up David.
This would be a great first PR if someone wants to take this on. One thing to consider is we'd like to keep backwards compatibility with SQLAlchemy 2.X for quite some time before dropping it. An ideal solution would work with both.
Hi @nickjj, I openend pull request #186 to address this issue.
Flask-SQLAlchemy 3 was just released, here's the changelog: https://flask-sqlalchemy.palletsprojects.com/en/3.0.x/changes/#version-3-0-0
Relevant changes for Flask-DebugToolbar are:
SQLALCHEMY_RECORD_QUERIES
is disabled by default and not enabled automatically with debug mode. You might want to show a warning if it's not enabled when using the debug toolbar.get_debug_queries
is renamed toget_recorded_queries
, and moved tofrom flask_sqlalchemy.record_queries import get_recorded_queries
.context
property is renamed tolocation
.The renames/moves currently show deprecation warnings, but will be removed in 3.1.