CommandError: Error applying evolution: (1050, "Table 'reviews_review_file_attachment_comments' already exists")

[John Schmitt]

Is there a work-around for this?

# rb-site upgrade /var/www/reviews.domain.com

Rebuilding directory structure
Updating database. This may take a while.


The log output below, including warnings and errors,
can be ignored unless upgrade fails.


------------------ <begin log output> ------------------
Creating tables ...
Upgrading Review Board from 1.5.5 to 2.0.17
There are unapplied evolutions for auth.
There are unapplied evolutions for contenttypes.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
There are unapplied evolutions for site.
Adding baseline version for new models
Evolutions in attachments baseline: file_attachment_orig_filename, file_attachment_file_max_length_512, file_attachment_repo_info, file_attachment_repo_path_no_index, file_attachment_repo_revision_max_length_64
Evolutions in site baseline: localsite_public
Evolutions in hostingsvcs baseline: account_hosting_url, account_hosting_url_max_length_255, account_unique_together_baseline
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database
CommandError: Error applying evolution: (1050, "Table 'reviews_review_file_attachment_comments' already exists")

[Christian Hammond]

This looks like another symptom of a very confused database. Are you starting from scratch every time you do an import + upgrade? It's not enough to drop individual tables. The entire database must be recreated.

Christian

--
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 reviewboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-- 
Christian Hammond - chri...@beanbaginc.com
Review Board - https://www.reviewboard.org

Beanbag, Inc. - https://www.beanbaginc.com

[John Schmitt]

My script drops the entire database then does a clean install.  Then I import my old mysql database and run `rb-site upgrade`.  

I'd really like to be able to finish this upgrade.  My struggle with it has been a couple of weeks now - I keep hoping that I'm doing something wrong and that posting my script would alert someone brighter than me that I could do something better and finish this.

Thanks for taking an interest.

You received this message because you are subscribed to a topic in the Google Groups "reviewboard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/21RErXZnLpo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to reviewboard...@googlegroups.com.

[Christian Hammond]

Hi John,

Yeah, I know this must be frustrating. I don't know why it's being so difficult, as we routinely have people upgrade from 1.0.x and 1.5.x to 2.0.x without problems.

If you're able to get me that list of SQL statements (from the `rb-site manage /path/to/site evolve -- --sql`) on a clean database import, it might help shed some light on this.

Can you also provide the result of: `rb-site manage /path/to/site list-evolutions`

Basically, what seems to be happening is that this intermediary table (managed by Django for some data we work with) is being created, and then an evolution is trying to create it again, which shouldn't be happening (and I'm not sure why it would). Having the data above would help in figuring out why this may be happening.

Just to provide this option, we offer support contracts for Review Board that, amongst other things, includes database repair/massaging. We take the dumps of the database and give you a dump back that works with the target release. We've done this for other companies at this point quite successfully.

Christian

--
Christian Hammond - chi...@chipx86.com

Review Board - https://www.reviewboard.org

Beanbag, Inc. - https://www.beanbaginc.com

[John Schmitt]

On Monday, July 6, 2015 at 2:41:34 PM UTC-7, Christian Hammond wrote:

Hi John,

Yeah, I know this must be frustrating. I don't know why it's being so difficult, as we routinely have people upgrade from 1.0.x and 1.5.x to 2.0.x without problems.

If you're able to get me that list of SQL statements (from the `rb-site manage /path/to/site evolve -- --sql`) on a clean database import, it might help shed some light on this.

What do you mean by "a clean database import"?  I have a clone of our running 1.5.5 installation.  Do you want the results of that command before I dump it?