I'm about to start using a database migration tool on an existing project. (Yes, yes, I know, I am crazy for not having done so from the beginning...)
So: south (the reigning champ) or nashvegas (the upstart)? I respect the people working on nashvegas a lot, and figure they have pretty good reasons for starting a new migration tool. And south seems more complicated (simpler is better, at least some of the time...). I read here http://www.issackelly.com/Blog/entry/On_Django_Migrations_South_vs_Nashvegas/ that "Much care has been made to make sure that you can start using south on your app part-way through development, where Nashvegas should really be used from the start. Converting to Nashvegas with a team requires though and planning, and with South, it requires one management command from each person (per app)." Still true? (Things move fast in the Django world.) Any other opinions, tips, warnings, gratefully received. -- 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.