Django+Postgres: “current transaction is aborted, commands ignored until end of transaction block”

Question

I\'ve started working on a Django/Postgres site. Sometimes I work in manage.py shell, and accidentally do some DB action that results in an error. Then I am una

Answer 1

If you happen to get such an error when running migrate (South), it can be that you have lots of changes in database schema and want to handle them all at once. Postgres is a bit nasty on that. What always works, is to break one big migration into smaller steps. Most likely, you're using a version control system.

• Your current version
• Commit n1
• Commit n2
• Commit n3
• Commit n4 # db changes
• Commit n5
• Commit n6
• Commit n7 # db changse
• Commit n8
• Commit n9 # db changes
• Commit n10

So, having the situation described above, do as follows:

• Checkout repository to "n4", then syncdb and migrate.
• Checkout repository to "n7", then syncdb and migrate.
• Checkout repository to "n10", then syncdb and migrate.

And you're done. :)

It should run flawlessly.