You have three choices.
1. Use South. #1 recommendation by me.
http://south.aeracode.org/
2. Delete your entire database and do another syncdb.
3. Write SQL manually to fix your database (don't do this).
The reason is that, once you do syncdb and a table is created, running
syncdb will never again touch that table. You need a schema migration
tool (South) for that.
Note that if you decide to use South and want to keep your existing
data, you'll have to revert your models.py to the state it was in during
the initial syncdb, create your 'initial' south migration, then make the
changes. Then you'll be able to use South to automatically create a
migration.
Shawn
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
