News for hackers. Stuff that matters.
Re:Django 1.5 released by cglace on Tuesday February 26, 2013 @10:49PM (#5290412)
The only thing I hated about django was using south for migrations. It was a huge headache.
Re:Django 1.5 released by jtchang on Wednesday February 27, 2013 @02:44AM (#5291187)
So what did you use instead?

Let me just say having migrations is a "good thing".

I know one place that just does SQL stuff by hand when they go to production. Seriously?!

Re:Django 1.5 released by cglace on Wednesday February 27, 2013 @10:08AM (#5292675)
I still used south for migrations I just found that I ended up editing the migration files for every migration.
Re:Django 1.5 released by rburhum on Wednesday February 27, 2013 @12:14PM (#5293443)
why? For the data migrations?
Re:Django 1.5 released by vhost- on Wednesday February 27, 2013 @12:18AM (#5290813)
The company I work for just switched _to_ south from a custom migration system and it has been really awesome. It streamlined out development process a bit as well.
Re:Django 1.5 released by bmelton on Wednesday February 27, 2013 @12:39AM (#5290894)
I never really loved them until I started working on a massive Django project with Oracle. South doesn't support Oracle, and now I have to manually tweak tables every time I update a schema.

Since that happened, I fricking love South.