Hi Gene, Looks like there was a partial attempt at an evolution that failed once before. The "visibility" column was applied and then something apparently went wrong, or upgrading was cancelled. Deleting the duplicates and running again would lead to this, unless carefully handled in a way compatible with django-evolution's internals.
Is this database schema the initial one applied from 2.0.25, or what you have on the test server after the upgrade attempts? Christian On Sun, Aug 13, 2017 at 8:40 PM, Gene Paul Quevedo <[email protected]> wrote: > Hi, > > I'ts my first time to post here, and I hope someone can point me to the > right way of solving this issue, even though it seems like there were > issues like this before > > I'm trying to do a DB upgrade of Review from 2.0.25 to 2.5.15 on a test > server with a copy of our Database, and seems like it has bumped into this > issue > > Rebuilding directory structure > Upgrading site settings_local.py > 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 ... > There are unapplied evolutions for accounts. > There are unapplied evolutions for attachments. > There are unapplied evolutions for diffviewer. > There are unapplied evolutions for reviews. > There are unapplied evolutions for webapi. > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > Installed 0 object(s) from 0 fixture(s) > > This may take a while. Please be patient, and do not cancel the upgrade! > > Applying database evolutions for accounts... > Database evolutions for accounts failed! > The SQL statement was: (u'ALTER TABLE `accounts_reviewrequestvisit` ADD > COLUMN `visibility` varchar(1) NOT NULL DEFAULT %s;', [u'V']) > > > > *The database error was: (1060, "Duplicate column name > 'visibility'")CommandError: Error applying evolution for accounts: (1060, > "Duplicate column name 'visibility'")* > There are probably 4 variations of that 'duplicate column' error, and the > other one is a 'duplicate index' . > My initial solution was to delete the duplicates and run the upgrade > procedure again, but seems like the duplication seems to be repeating (!), > as if Django Evolution is creating those duplicate columns/indices > > Any ideas on how to debug this further? I'm attaching our DB schema here > > thank you! > - Gene > > -- > 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. > -- Christian Hammond President/CEO of Beanbag <https://www.beanbaginc.com/> Makers of Review Board <https://www.reviewboard.org/> -- 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.
