On 8/25/06, Dave <[EMAIL PROTECTED]> wrote: > > I create my models in models.py, and everything looks great. I launch > the application and millions upon millions of peope start using my app > and creating their own little entries in my database, via the perfect > models.py I wrote. > > But then, the EVIL CLIENT comes along and requests a change to existing > functionality that requires a change to the model... > > What do I do about my millions upon millions of users, with vital, life > affirming and threatening data stored in the database? I can't change a > model and then have it change the database without destroying all their > information? Or is there some aspect of manage.py I've completely > missed? > > If this is simple and I'm missing the point entirely, feel free to hit > me in the head with a brick. Softly. >
Right now, the only option is to manually run whatever SQL commands are required to convert the schema to match your new model(adding/dropping columns, tables, etc). You can use manage.py to show what the schema should look like for your new model, then figure out the SQL commands on your own. There is a Summer of Code project for Django schema migration, which should do the above steps automatically. Not sure of the current progress of it (though I'd guess it'll be done soon). Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
