On Sun, 2006-08-20 at 09:43 -0700, bayerj wrote: > As soon as I change my database schema, I have several possibilites to > get my app up again: > (a) Change the model. Then drop the current db schema, fire up the new > one. Drawback: I lose my data. > (b) Change the model and change the schema manually. Drawback: I am > repeating myself. > (c) Make everything right from the start. Drawback: Can only be reached > asymptotical. (I won't argue about that :)
There's a Google Summer of Code project going on at the moment to support model evolution throughout a project's development. I haven't played with it, but I've heard it's coming along. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
