I have to concur with Max here. I know it sounds like a pain to migrate schema changes BY HAND...but trust me, the tools don't help that much. I'm a DBA in my day job (MS SQL, Oracle, and Postgresql primarily), and the majority of the problems that occur when developers are trying to do application migrations are from auto-DDL generation tools. And it gets to be kind of a big deal when your have a public-facing application or something...*grin*
That being said, I'm a big fan of automated assistance in this area, but don't blindly rely on it. A place to start is "what objects are different" between dev and prod (or ideally, testing. *grin*). Just that list is helpful, as it'll keep you from missing something obvious. Start with this list, and it'll make things simpler to deal with w/o automagically breaking your nice production app! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
