It would be in your benefit to learn why South failed, because it's been very stable for me, and may be an indication of something else being wrong with your app and/or models.
-- Michael <mhall...@gmail.com> On Tue, 2010-11-02 at 15:27 -0400, Sells, Fred wrote: > I've got my first major django production app deployed and have to > upgrade my DB to meet some new requirements. I've tried South, but got > into a death spiral and my changes are not so significant that I can't > do it by brute force. > > In researching brute force, it seems like syncdb loads my initial tables > from the .../myqpp/sql/xyz.sql files just fine. > > So what do I achieve with manage.py sqlall myapp -- I don't see the > value and the docs don't say why, only how. > > Right now I'm planning to > 1. use drop/create database to assure a blank slate > 2. use syncdb to create my new tables > 3. use >mysql mydbname <mydbdump.sql #which was created with the > options to not include structure, just insert statements > 4. Imay need to reload the data in myapp/sql directory because may wipe > it out. > > Basically the first 10 records in each table contain a template pattern > of which fields are disabled under certain circumstances, and that data > has changed slightly for 2 tables. > > South may make more sense in the future, but I'm up to my #$%%# in > alligators and the swamp must wait. > > Is there anything I'm missing or am I doing something "the hard way"? > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
