On 12/4/06, marksibly <[EMAIL PROTECTED]> wrote: > > > I initially thought 'manage.py syncdb' would detect and handle this for > you, but it doesn't appear to.
No - Syncdb will add any completely new model, but will not alter any existing model. The behaviour you are seeking is under development in the schema evolution branch. I don't know the status of this branch for certain; it was the subject of a Google 'summer of code' project, and I believe that the engineering work is complete, but requires feedback and review before it is committed to the trunk (I could be wrong on this - anybody in the loop on this stream care to comment?) Anyway - the wiki describes what was intended for this stream: http://code.djangoproject.com/wiki/SchemaEvolution Currently, I'm using MySql to 'DROP TABLE' and then using 'manage.py > syncdb' again, but this seems a bit cumbersome. As an alternate to DROP TABLE, you can use ./manage.py reset [appname] - this will execute the required DROP TABLE calls on the database. Yes, it is cumbersome, but its the best we can offer at the moment. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
