Hello, It is correct. Syncdb will not alter existing tables:
http://docs.djangoproject.com/en/1.2/ref/django-admin/#syncdb The reason is that if you've changed you model with some kind of constrains (unique fields, etc), Django will not try to guess how to mantain the correctness of your data. It is your task. Renne Rocha renne.ro...@gmail.com http://www.linkedin.com/in/rennerocha On Tue, Aug 24, 2010 at 11:17 AM, Sithembewena Lloyd Dube <zebr...@gmail.com> wrote: > Hi all, > > I have been working on some models and tried to run the manage.py syncdb > command. It says there are no fixtures found even after I just added a field > to a model. > > A solution has been to drop the table in MySQL before running syncdb. This > doesn't seem feasible all the time. What could I be doing wrong? > > Thanks > > -- > Regards, > Sithembewena Lloyd Dube > http://www.lloyddube.com > > -- > 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. > -- 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.
