5👍
✅
From the output, it seems like the database is already synchronized with the migrations. There are no problematic errors. (Although you shouldn’t really be root to run the migrations.)
If you’re looking into creating more migrations, use the south documentation, which usually is just running the following after you modify the models:
python manage.py schemamigration --auto <APP>
And then use python manage.py migrate
to apply the changes.
👤Jeff
1👍
It looks like migrations have been already passed. Check south_migationhistory table in db.
If you want to sync new db for apps which has migrations just disable south in settings.py.
1👍
Have you ran a schemamigration initial yet?
./manage.py schemamigration deals --initial
./manage.py migrate deals
if you get the error, db already excists do this:
./manage.py schemamigration deals --initial
./manage.py migrate deals --fake
- [Django]-Django Formset Missing Management Form Data
- [Django]-Celery with redis backend
- [Django]-Named JSON array in Django REST Framework
- [Django]-Django Rest Framework: PUT/POST fails in case of blank optional fields in nested serializer
Source:stackexchange.com