flask-db VS flask-restful

When I updated Flask 1 to 2 I didn't encounter any issues with migrations but I also use Flask-DB not Flask-Migrate. Everything worked great.

I've written https://github.com/nickjj/flask-db which is a Flask extension that makes using Alembic a bit more convenient and also adds quality of life improvements like being able to reset and create your main / test database and run a "seed" command to seed your DB with initial data.

It looks like you have Flask-DB installed which is an alternative library to Flask-Migrate. Flask-DB is something I wrote btw which uses Alembic to handle the migrations, that's the official SQLAlchemy DB migration tool.

If anyone happens to use SQLAlchemy, Alembic and Flask a while back I open sourced a Flask CLI extension called Flask-DB at https://github.com/nickjj/flask-db.

Its focus is to quickly init Alembic configs with a few opinions, alias the official Alembic CLI for migrations and also let you quickly reset and seed your database using patterns found in other frameworks (such as having a seeds.py file that you can do whatever you want in).

Flask-DB for database migrations and initializing / seeding your DB

When it comes to Flask, in particular, there’re plenty of choices. And in fairness, not all frameworks are created equal. You’ve got flasgger, restx (successor of flask-restplus), flask-RESTful, and flask-smorest, to mention a few. How do you choose among those???

This has talked about in a similar matter: https://github.com/flask-restful/flask-restful/issues/221. However I'm still adamant about just using flask for exception handling. Unless I missed something,I'm having a hard time figuring out how to accomplish this in hopes to get rid of the string concatenation that flask_restful applies to the error message.

Considering the extension you've mentioned explicitly, the author of it has provided an explanation as to why he is not longer putting in any work, you can read about it here.