django syncdb and an updated model
Question:
I have recently updated my model, added a BooleanField to it however when I do python manage.py syncdb, it doesn’t add the new field to the database for the model. How can I fix this ?
Answers:
Havent used django in a while, but i seem to remember that syncdb does perform alter commands on db tables. you have to drop the table then run again and it will create again.
edit: sorry does NOT perform alter.
From Django 1.7 onwards
Django has built in support for migrations – take a look at the documentation.
For Django 1.6 and earlier
Django doesn’t support migrations out of the box. There is a pluggable app for Django that does exactly that though, and it works great. It’s called South.
Django currently does not do this automatically. Your options are:
- Drop the table from the database, then recreate it in new form using syncdb.
- Print out SQL for the database using
python manage.py sql (appname), find the added line for the field and add it manually using alter table SQL command. (This will also allow you to choose values of the field for your current records.)
- Use South (per Dominic’s answer).
As suggested in top answer, I tried using South, and after an hour of frustration with obscure migration errors decided to go with Django Evolution instead.
I think it’s easier to get started with than South, and it worked perfectly the first time I typed ./manage.py evolve --hint --execute, so I’m happy with it.
If you run Django with Apache and MySQL, restart apache after making migration with makemigrations.
In django 1.6
-
At first we have run – python manage.py sql <app name>
-
Then we have to run – python manage.py syncdb
I have recently updated my model, added a BooleanField to it however when I do python manage.py syncdb, it doesn’t add the new field to the database for the model. How can I fix this ?
Havent used django in a while, but i seem to remember that syncdb does perform alter commands on db tables. you have to drop the table then run again and it will create again.
edit: sorry does NOT perform alter.
From Django 1.7 onwards
Django has built in support for migrations – take a look at the documentation.
For Django 1.6 and earlier
Django doesn’t support migrations out of the box. There is a pluggable app for Django that does exactly that though, and it works great. It’s called South.
Django currently does not do this automatically. Your options are:
- Drop the table from the database, then recreate it in new form using syncdb.
- Print out SQL for the database using
python manage.py sql (appname), find the added line for the field and add it manually usingalter tableSQL command. (This will also allow you to choose values of the field for your current records.) - Use South (per Dominic’s answer).
As suggested in top answer, I tried using South, and after an hour of frustration with obscure migration errors decided to go with Django Evolution instead.
I think it’s easier to get started with than South, and it worked perfectly the first time I typed ./manage.py evolve --hint --execute, so I’m happy with it.
If you run Django with Apache and MySQL, restart apache after making migration with makemigrations.
In django 1.6
-
At first we have run –
python manage.py sql <app name> -
Then we have to run –
python manage.py syncdb