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!)
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.
Reliable Askbot Hosting
Create your Q&A site at askbot.com. Managed Askbot hosting at just $15/mo. Dedicated hosting, support contracts, consulting services.
create your Q&A site30 days free trial
Stats
Asked: 2012-04-12 12:46:04 -0500
Seen: 25 times
Last updated: Apr 21 '12
Could you provide more details on how do you run migrations? Migrations works for me
Fitoria ( 2012-04-12 16:05:52 -0500 )editWhich version of postgres do you have?
Evgeny ( 2012-04-13 18:12:38 -0500 )edit