Not sure if you've received a fix yet but i just wanted to share that I too 
had issues upgrading from 1.6 to (1.7.25 and 2.0.5).
To fix the upgrade issue in my case I made MyISAM the default for MySQL 
before creating and restoring the database.

Add the following line under [mysqld] in my.conf:
default-storage-engine=MyISAM

You can of course just set a single Database to use it instead of the 
entire install (just in case you run another application on the same box).

I should probably also mention i had issues going to 2.0.5 even with this 
fix. The upgrade worked great but we would receive random error pages when 
trying to create a new Diff.
2.0.6 Worked flawlessly for me.

Steven Richards

On Monday, September 22, 2014 8:13:37 AM UTC-4, Kenneth Wong wrote:
>
> Hi Christian, looks like all of the tables are using the InnoDB engine. 
>  The commands I used inside mysql were:
>
> use rb2;
> show table status;
>
> On Sunday, 21 September 2014 22:24:09 UTC-4, Christian Hammond wrote:
>>
>> Hi Kenneth, 
>>
>> Can you determine if the tables being created are using InnoDB or MyISAM? 
>> Or a mix? 
>>
>> Christian 
>>
>> -- 
>> Christian Hammond - chri...@beanbaginc.com 
>> Review Board - https://www.reviewboard.org 
>> Beanbag, Inc. - https://www.beanbaginc.com 
>>
>>
>> On September 21, 2014 at 7:18:11 PM, Kenneth Wong (lost...@gmail.com) 
>> wrote: 
>> > Hi, I'm upgrading from 1.6.4.1 to 2.0.5 as well as transitioning from 
>> > sqlite to mysql. I'm looking for some help on understanding the error 
>> > messages and what I can do about it. 
>> > 
>> > As per Christian's recommendation (from another thread), I did the 
>> > following: 
>> > 
>> > 1. Create a brand new 2.0.5 reviewboard site that uses sqlite. (rb1) 
>> > 2. Copied over the 1.6.4.1 reviewboard.db file. 
>> > 3. Performed "rb-site upgrade rb1". I had to run a couple of other 
>> > changes from the commandline such as: 
>> > 1. removing the old authentication backend 
>> > 2. adding in active directirectory authentication 
>> > 4. Performed "rb-site manage rb1 condensediffs" 
>> > 5. Also performed all the necessary permission changes 
>> > 
>> > From there I was able to log in to the new site... very nice. At this 
>> > point, I'd like to be able to switch over to mysql... there's enough 
>> > traffic on the site to definitely warrant a more solid database 
>> backend. I 
>> > did the following: 
>> > 
>> > 1. Create a brand new 2.0.5 reviewboard site that uses mysql (rb2) 
>> > 2. Performed "rb-site manage rb1 dumpdb > rb1.json" 
>> > 3. Performed "rb-site manage rb2 loaddb rb1.json" 
>> > 
>> > Lots of errors flew by... ended up with a "done" message and a 
>> reviewboard 
>> > that I could log into but that's definitely broken. 
>> > 
>> > There were two types of errors, the first being foreign key constraint 
>> > failures (such as the one below): 
>> > 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`django_admin_log`, CONSTRAINT 
>> > `user_id_refs_id_c0d12874` FOREIGN KEY (`user_id`) REFERENCES 
>> `auth_user` 
>> > (`id`))') 
>> > 
>> > And the other were Duplicate Entry errors such as: 
>> > 
>> > - Error: (1062, "Duplicate entry 'changedescs-changedescription' for 
>> key 
>> > 'app_label'") 
>> > 
>> > Below are the remaining unique foreign key constraint failures that 
>> came up 
>> > (multiple instances of each): 
>> > 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`auth_permission`, CONSTRAINT 
>> > `content_type_id_refs_id_d043b34a` FOREIGN KEY (`content_type_id`) 
>> > REFERENCES `django_content_type` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`accounts_reviewrequestvisit`, CONSTRAINT 
>> > `review_request_id_refs_id_0943e99f` FOREIGN KEY (`review_request_id`) 
>> > REFERENCES `reviews_reviewrequest` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`accounts_profile_starred_review_requests`, 
>> > CONSTRAINT `reviewrequest_id_refs_id_342ff1ac` FOREIGN KEY 
>> > (`reviewrequest_id`) REFERENCES `reviews_reviewrequest` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`accounts_localsiteprofile`, CONSTRAINT 
>> > `local_site_id_refs_id_02a402db` FOREIGN KEY (`local_site_id`) 
>> REFERENCES 
>> > `site_localsite` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`diffviewer_filediff`, CONSTRAINT 
>> > `diffset_id_refs_id_c4a01a9e` FOREIGN KEY (`diffset_id`) REFERENCES 
>> > `diffviewer_diffset` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`diffviewer_diffset`, CONSTRAINT 
>> > `history_id_refs_id_153db9d3` FOREIGN KEY (`history_id`) REFERENCES 
>> > `diffviewer_diffsethistory` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`diffviewer_diffset`, CONSTRAINT 
>> > `repository_id_refs_id_76fa8bca` FOREIGN KEY (`repository_id`) 
>> REFERENCES 
>> > `scmtools_repository` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_defaultreviewer`, CONSTRAINT 
>> > `local_site_id_refs_id_c0a6afc5` FOREIGN KEY (`local_site_id`) 
>> REFERENCES 
>> > `site_localsite` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_comment`, CONSTRAINT 
>> > `filediff_id_refs_id_828a3cce` FOREIGN KEY (`filediff_id`) REFERENCES 
>> > `diffviewer_filediff` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_comment`, CONSTRAINT 
>> > `reply_to_id_refs_id_fd1965c8` FOREIGN KEY (`reply_to_id`) REFERENCES 
>> > `reviews_comment` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_reviewrequest`, CONSTRAINT 
>> > `local_site_id_refs_id_7b3d9679` FOREIGN KEY (`local_site_id`) 
>> REFERENCES 
>> > `site_localsite` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_review`, CONSTRAINT 
>> > `review_request_id_refs_id_c50f4370` FOREIGN KEY (`review_request_id`) 
>> > REFERENCES `reviews_reviewrequest` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`reviews_reviewrequestdraft`, CONSTRAINT 
>> > `review_request_id_refs_id_1b41e63e` FOREIGN KEY (`review_request_id`) 
>> > REFERENCES `reviews_reviewrequest` (`id`))') 
>> > - Error: (1452, 'Cannot add or update a child row: a foreign key 
>> > constraint fails (`rb2`.`scmtools_repository`, CONSTRAINT 
>> > `local_site_id_refs_id_a0854215` FOREIGN KEY (`local_site_id`) 
>> REFERENCES 
>> > `site_localsite` (`id`))') 
>> > 
>> > I have the full log if anyone thinks that it might help. 
>> > 
>> > Thanks in advance, 
>> > Ken. 
>> > 
>> > -- 
>> > Get the Review Board Power Pack at 
>> http://www.reviewboard.org/powerpack/ 
>> > --- 
>> > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ 
>> > --- 
>> > Happy user? Let us know at http://www.reviewboard.org/users/ 
>> > --- 
>> > You received this message because you are subscribed to the Google 
>> Groups "reviewboard" 
>> > group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to reviewboard...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/d/optout. 
>> > 
>>
>>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to