Sorry to hear you got bit by some failed upgrade problem. All upgrades *should*
be done in one transaction.
It's *possible* that this is really a problem of some upgrade metadata that is
screwed up. Something to try is:
$ rb-site manage /path/to/site shell
>>> from django_evolution.models import Version
Back up the database first, though.
Once you run that, try to do an upgrade again.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Jan 22, 2013, at 1:50 PM, christophe.one...@gmail.com wrote:
> After some investigation, the reported error above was easily fixed.
> As it is clearly explained here, on Windows the default configuration of
> MySql doesn't allow default value for BLOB type. Setting sql_mode to
> "MYSQL40" in my.ini solves the problem.
> But an error can hide another, and at the next run rb-site complained about a
> field "diff_base64" which couldn't be added because it was present already.
> I guess that the origin of the problem is a previous unsuccessful upgrade
> attempt to reviewboard 1.7. Some database changes shouldn't have been
> reverted properly.
> This database schema problem could be very difficult to fix, I think I'm
> better off setting up a new reviewboard site from scratch. And from now
> backing up my database before every upgrade !
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at