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

Add to README Section on Why use Flask-Migrate vs just Alembic #101

Closed
cancan101 opened this issue Feb 22, 2016 · 3 comments
Closed

Add to README Section on Why use Flask-Migrate vs just Alembic #101

cancan101 opened this issue Feb 22, 2016 · 3 comments
Assignees

Comments

@cancan101
Copy link

As a potential new user of Flask-Migrate, I looked for a section in the README as to why use Flask-Migrate instead of just using the CLI that comes with alembic.

@miguelgrinberg
Copy link
Owner

Okay, fair point. The reason is that Flask-Migrate gives you a zero configuration set up when using Flask-SQLAlchemy, Flask-Script and Alembic. You can use Alembic alone, but you'll have to do some configuration work, as Alembic knows nothing about Flask or Flask-SQLAlchemy.

@Guttz
Copy link

Guttz commented Mar 18, 2019

What about a flask application but with sqlalchemy and not flask_sqlalchemy? Does it work/requires zero configuration? I'm currently making the decision for a project @miguelgrinberg

@miguelgrinberg
Copy link
Owner

This package works with Flask-SQLAlchemy. If you are using plain SQLAlchemy you can't use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants