Hi Dan,
This sort of information actually comes at a level lower than what we deal
with. It's during Django's table building process, and we have no insight
or control into any of that. I agree that this would be *very* nice (and we
need to document it), but as for creating a better error or knowi
I too had this issue (MySQL default changing from MyISAM to InnoDB).
Although I understand that this is caused by MySQL version being updated at
the same time as a Reviewboard Update (and migrate).
But would there be any way for the 'upgrade' logic of Reviewboard to post a
more useful error messa
