Schema migration is not an option, it is required for any production code (we ship a lot of code to out customer's site and regularly publish patches that include schema changes). You cannot make a site without ORM or schema migration, I see both at the same level.
BTW, we use django evolution since south doesn't support python 2.3 (again a lot of enterprise code is stuck at RHEL4 which is py2.3) Rui On Oct 23, 8:35 pm, James Bennett <ubernost...@gmail.com> wrote: > On Fri, Oct 23, 2009 at 5:12 AM, rjc <coelho....@gmail.com> wrote: > > The only reason I will migrate to 1.2 is if you include schema > > migration. It is that important for us (we have a lot of production > > code out). Anyway, why did we pick south instead of django-evolution ? > > I'm +1 (+1 +1) for any db schema migration. > > Guess you're gonna stay with 1.1 for a while. > > Seriously, why is it so difficult to use a solution you already have? > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
