A fixed migration is the code run to get from one step to another. Migrations uses the, maybe at some point you needed to add an extra table to the db. Then you could write a migration that would add the table if you wanted to progress or delete the table if you wanted to get back. You would have that list with app and when you install the app elsewhere you could choose at which point in the migration history you wanted your database in. Maybe for some testing you needed the database like it was at some point. Evolution works differently, it looks at the db and compares it to the models and the try to make the changes needed when you run syncdb. So in order to controll evolutions you would need to change to model fields.
On 7 Mar., 23:59, Ben Davis <bendavi...@gmail.com> wrote: > I've been looking into both the "South" and "django-evolution" migration > frameworks. There are things I like about both of them, although I'm > leaning towards django-evolution. > > The thing I like about django-evolution is that migrations are described in > the same "language" as your model, that is, instead of adding/removing > tables & columns, we're adding/removing models and fields, which is (I > believe) the way it should be. I don't feel like "create_table()" is any > different from SQL's "CREATE TABLE". > > However, the author of South > claims<http://south.aeracode.org/wiki/Alternatives>to have started the > project out of frustrations with django-evolution. I've > read those points, and having a really difficult time understanding what > they really mean. What do they mean by migartions not being "fixed in the > codebase", and "fixed migrations are all run when an app is first > installed" ? What exactly are "fixed migrations" anyways? I'd love to > understand these points as I don't want to regret choosing django-evolution. > > I haven't looked into dmigrations that much, but if anyone has any input on > that I'm all ears. > > Thanks!! --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
