On Thu, 2007-02-15 at 04:54 +0000, akonsu wrote: > hello, > > in my models.py i have two classes related as many-to-many. if i add a > ManyToManyField to one of the models, and run manage.py reset or > syncdb, and then move the field to the other model (which functionally > makes no difference) and run manage.py reset again, it fails to reset > the database because it tries to remove tables in a wrong order. is > this a bug? should i open a ticket? > > in general it seems that the code that resets the database uses the > models and not the database itself to find the table dependencies when > removing tables. which i think is wrong...
Because we haven't merged schema evolution into the trunk yet, any cases where you change portions of a model are meant to result in you editing the database by hand. Syncdb (and django/core/management.py in general) do not have the smarts to really handle schema changes yet. Schema changes do involve looking at the database to work out what has changed, as you indicate. One day we will merge in the schema-evolution branch to trunk and this will work for many popular cases. Until then, if you change your models, dump the SQL output (via "manage.py sql ...") and make any changes you want to by hand. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
