fix: get_bind for SQLAlchemy and Flask-SQLAlchemy

[dpgaspar]

Description

This is still pending by Flask-SQLAlchemy latest release

Unpins SQLAlchemy below 1.4.X.

This is still pending, new SQLAlchemy 1.4.18 fixes the positional arguments on Session subclasses, but current Flask-SQLAlchemy still is not correct since it's missing the bind parameter when calling super.get_bind. Latest (yet to be released) Flask-SQLAlchemy is correct (version 3.0.0)

pallets-eco/flask-sqlalchemy#953

ADDITIONAL INFORMATION

• Has associated issue: ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed #1648 Any plans to update to SQLAlchemy 1.4.11 (it currently resets SQLAlchemy to 1.3.24) #1621
• Is CRUD MVC related.
• Is Auth, RBAC security related.
• Changes the security db schema.
• Introduces new feature
• Removes existing feature

[ashb]

Hey @dpgaspar Anything I can do to help land this? Would it be useful if I tested this change against Airflow?

[dpgaspar]

Hey @dpgaspar Anything I can do to help land this? Would it be useful if I tested this change against Airflow?

@ashb thanks for reaching out, I'm waiting for flask-sqlalchemy 3.0.0 release that would solve this, but it's taking some time. I'll revisit flask-sqlalchemy PR for 2.5.X and ask them to release a 2.5.2 (may have time next week)

https://github.com/pallets/flask-sqlalchemy/blob/main/CHANGES.rst#version-300

[ashb]

Cool. I'm just itching to start playing around with async support from SQLAlchemy 😁

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Feel free to reopen it if it's still relevant to you. Thank you