Postgres + Django + South = Frustration

Posted on March 2, 2014

I just applied a South migration which then caused this blog to break. The error that I was seeing was that the new field that I added, 'is_published', a Boolean field, was not a column. I did everything else that I've done 100 times:

python syncdb
python schemamigration blog --auto
Then I committed all of the new code to git and pushed to Heroku
lastly, heroku run python migrate

Normally this works just fine, but for some reason, this broke my app.

After 1.5 hours of trying to figure out what to do, I realized it would be easiest to deploy a new database and then recover my old blog posts later.

Does anyone have a better system for using Heroku and Postgres? Am I just doing something wrong in applying South migrations? Could it be an issue related to the new field being a Boolean?

If reference is needed, all of my code for this blog is available here.