Thanks, that solved the issue. Looks like mysql 5.5 defaults to InnoDB but
our original tables were in the older format. I altered them to InnoDB and
everything works now. Thanks,
--Erik
On Tuesday, June 25, 2013 4:26:12 PM UTC-4, Christian Hammond wrote:
>
> That error has to do with having a m
That error has to do with having a mix of InnoDB and MyISAM tables. You
need to make sure all tables are the same format. If MySQL is creating new
tables with one, then you should convert the rest.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Bea
I'm getting the exact same error. I'm trying to test an upgrade before
actually performing one on the live server and am getting the same Django
stack trace.
We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using
easy_install to install ReviewBoard and made sure to force the Dja
