Comments (4)
The db.create_all()
call at the end of your models module should be removed. When you use Flask-Migrate the creation of tables is handled by the extension.
Try the following: remove that db.create_all()
call, then delete all your database tables. Check in your migration/versions
folder and if you have any files there remove them as well. Now call app_db.py db migrate
. This should generate a migration that should include your tables. Review the new script added in migrations/versions
and once you are satisfied with it run app_db.py db upgrade
to trigger the creation of the tables in the database.
from flask-migrate.
Closing due to inactivity. I assume you worked out your problem, if not please reopen.
from flask-migrate.
@miguelgrinberg i don't think it's necessary to drop all the db tables (especially when you have important information in them)....in my case i simply:
- commented out
db.create_all()
- then i deleted the new table that was created
after that alembic detected the new table and the migration worked without any problem
from flask-migrate.
@danidee10 you need to delete only the tables that you want the migration to pick up. In the case of this issue, the OP needed all the tables added to the migration, that is why I recommended all of them to be dropped.
from flask-migrate.
Related Issues (20)
- Flask Boolean Question HOT 1
- Upgrade problems; Online migration expected to match one row error HOT 1
- Alembic upgrade head in infinite loop HOT 1
- Migrations sometimes end with status 1 HOT 4
- How to check if models are in sync with generated migrations? HOT 1
- Type hints HOT 2
- [4.0] app factory is called before click groups HOT 6
- flask db migrate taking ~30min to autogenerate and throwing unrelated warnings HOT 2
- How is this possible?
- Failure to run flask db migrate after upgrade 3.1 -> 4.0 HOT 4
- Custom Template is not included in the sdist HOT 1
- Compatibility with sqlalchemy v2 HOT 5
- DeprecationWarning: 'get_engine' is deprecated HOT 5
- Enum Field changes, but no changes in schema detected when run "flask db migrate" HOT 1
- Do not automatically import of sqlalchemy_utils HOT 1
- The pgvector vector field cannot generate a normal migration script HOT 1
- An error was reported during migration
- [Feature request] Move `process_revision_directives` to `alembic_ctx_kwargs` HOT 2
- Problems connecting to Postsgress Because of no encryption HOT 5
- No such command 'db'
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flask-migrate.