Comment #9 on issue 3486 by robottom...@gmail.com: Upgrade 2.0 to 2.0.3
fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
We had the same issue going from 2.0 to 2.0.5 using postgres as the
database. We followed this workaround and it worked.
--
You received this message
Comment #8 on issue 3486 by chip...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
What database?
Happen to have a dump of your 2.0.1 available still?
--
You received this message because this project is configured to send all
issue
Comment #7 on issue 3486 by rick...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
Got the same issue when upgrading from 2.0.1 to 2.0.5. Manually fixed with
Abhishek's commands.
--
You received this message because this project is
Comment #5 on issue 3486 by abhishek.mukher.g: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
This, from the sounds of it, might have been fixed by 2.0.5? The release
notes suggest django-evolutions changes. not sure if that encompasses
this or not.
Updates:
Status: Fixed
Comment #6 on issue 3486 by trowb...@gmail.com: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
Yes, this should be fixed by 2.0.5
--
You received this message because this project is configured to send all
issue
Comment #1 on issue 3486 by abhishek.mukher.g: Upgrade 2.0 to 2.0.3 fails
http://code.google.com/p/reviewboard/issues/detail?id=3486
I had this issue as well. I don't quite get what django evolutions is up
to; it seems like it's trying to drop a constraint instead of an index. I'm
not
