Update: tried rb-site manage /path/to/site evolve -- --hint --execute but ends with Duplicate column error (password , or permission)
hmm. further research it may not be due to our customization , but another case that the database somehow is in a bad state. I recall reading from some posts then manual manipulation of database schema is not recommended. On Wednesday, January 13, 2016 at 1:06:43 PM UTC-5, Jasper Chow wrote: > > > Attach evolve log ( rb-site manage /var/www/reviewboard evolve -- --hint > ) for diagnosis > > thanks > > > On Tuesday, January 12, 2016 at 12:58:01 PM UTC-5, Jasper Chow wrote: >> >> Hello >> >> I am having issue similar to previous reported, while running rb-site >> upgrade >> >> https://hellosplat.com/s/beanbag/tickets/3967/ >> https://www.mail-archive.com/[email protected]/msg15947.html >> >> >> information: >> on Linux (CentOS) reviewboard 1.7 -> 2.0.16 ( intended to upgrade to >> latest but ran into some problem, thought I would do it with a smaller >> increment ) >> >> >> easy_install ReviewBoard==2.0.16 (successful) >> rb-site upgrade [path] fails with following error: >> >> >> >> In model reviews.ReviewRequest: >> Field 'related_review_number' has been deleted >> In model reviews.Review >> Field 'notify_only_submitter' has been deleted >> In model reviews.ReviewRequestDraft >> Field 'related_review_number' has been deleted >> In model accounts.Profile >> Field 'eclipse_diff_view' has been deleted >> >> >> Judging by the name of the columns it seems some customization done by >> previous admin here. So question is >> What is the best practice to migrate these extension columns? >> >> >> I tried >> - drop the columns from the database ( and to restore them later ) , and >> run upgrade again >> - or used the trick provided in another post >> >> >>> from django_evolution.models import Version >> >>> v = Version.objects.all()[0] >> >>> print v >> Hinted version, updated on 2015-02-12 02:23:19+00:00 >> >>> v.delete() >> >>> >> >> but it doesn't seems to help either >> >> Or maybe it should be other way around that I need to modify the schema >> somewhere before i run the upgrade script? >> >> any help / suggestion is appreciated.. thank you >> >> >> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 [email protected]. For more options, visit https://groups.google.com/d/optout.
