On 5/11/07, James Bennett <[EMAIL PROTECTED]> wrote: > > On 5/11/07, Nic James Ferrier <[EMAIL PROTECTED]> wrote: > > Something needs to be done though... or ongoing maintenance of Django > > apps is going to be really hard. > > I haven't found it terribly hard with a little coding discipline; the > way we've handled it is to write the necessary SQL and commit it to > our repository along with model changes, so we have a history of how > the model has evolved over time. Some way of specifying "revision > numbers" of models and having Django find the necessary SQL files to > execute (where those files were manually constructed) is really all > the automation I'd like to see :)
I can't speak for others, but I'd like to see a little more than that. The Wiki page about schema evolution [1] has a decent set of ideas. >From that document, specifying raw SQL for model transforms is a necessary, but not sufficient feature. I tend to agree. [1] http://code.djangoproject.com/wiki/SchemaEvolution 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 -~----------~----~----~----~------~----~------~--~---
