James Bennett 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 :)
Thats pretty much what DbMigration does: http://www.aswmc.com/dbmigration/ Instead of a single version number it uses named updates and stores the updated performed in a table. Updates can be defined in SQL or Python functions. I have been using it for about three weeks with a database under pretty frequent modification (10 schema changes in those 3 weeks) and I am very pleased with it. It includes a patch to syncdb so updates run with syncdb. Kent --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
