News for hackers. Stuff that matters.
Re:How to Tango with Django: A Python Django Tutorial by frankwiles on Tuesday October 22, 2013 @11:16AM (#6592448)
Absolutely agree. Even something as simple as adding an optional field is just ./manage.py schemamigration --auto <appname> and you're done vs "ALTER TABLE blah blah blah...." on your local system, dev/staging, and then again on production in the right order, every time, manually. Can't imagine anyone wanting to go back to manual after using South.
Re:How to Tango with Django: A Python Django Tutorial by rmrfrmrf on Tuesday October 22, 2013 @01:14PM (#6593308)
This thread perfectly exemplifies the frustration laid out in my original post.
Re:How to Tango with Django: A Python Django Tutorial by jaegerpicker on Tuesday October 22, 2013 @04:53PM (#6594905)
Welcome to development with open source technology. It takes time and effort to figure out the best practices. There is no magic bullet, sorry. That's not meant to be snarky it's just the way the process works.
Re:How to Tango with Django: A Python Django Tutorial by collyw on Wednesday October 23, 2013 @03:25PM (#6601066)
And use Postgres as the database. If you use MySQL you will get sick of South telling you to use Postgres whenever a migration doesn´t go smoothly.