First time here? Check out the FAQ!

Why is askbot migration 0032 broken?

There is a unique index being added to askbot_badgedata which aleady has unique=True when it's created a couple lines earlier. I discovered it doing a clean install using Postgres as the DB. I don't really understand South, but shouldn't an old migration stay the same?

(this is mostly a bug report, but I wasn't sure where to put it since you aren't using github issues!)

JeffJenkins's avatar
asked 2012-04-12 12:46:04 -0500
edit flag offensive 0 remove flag close merge delete



Could you provide more details on how do you run migrations? Migrations works for me

Fitoria's avatar Fitoria (2012-04-12 16:05:52 -0500) edit

Which version of postgres do you have?

Evgeny's avatar Evgeny (2012-04-13 18:12:38 -0500) edit
add a comment see more comments

1 Answer


There is a bug in South migration app version 0.7.3 with the setup of unique constraints.

In askbot version 0.7.42 we added a workaround for this issue to the migration, should work now.

Evgeny's avatar
answered 2012-04-21 09:51:15 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments