Running syncdb on an already-existing model won't make the changes in the database. For that, you should employ the fine services of South. south.aeracode.org/
At this point, you might be best served by the following procedures: 1. Put the field back in your model. 2. Install South, add it to installed_apps. 3. Run: ./manage.py convert_to_south appname #only needed once, to teach South about your current schema 4. Remove the field from your model. 5. Run: ./manage.py startmigration your_app_name description_of_change --auto 6. Run: ./manage.py migrate Let me know if you have any trouble or questions with South. 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-us...@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.
