I stepped through the django_evolution code in Command.evolve() and
found that it seems to be unconditionally trying to issue these ALTER
statements. I'm not sure why it's doing that - seems ridiculous.
I tried manually dropping that basedir column to appease the program
(all the values were
Hm, one of my prior emails seems to have been dropped. Anyway, I'd
appreciate any help on this - otherwise looks like we're stranded.
On Tue, Dec 20, 2011 at 8:55 PM, Yang Zhang yaa...@gmail.com wrote:
For what it's worth, I'm upgrading from 1.5.1 to 1.6.3 right now and I just
encountered the
I should probably also add that this is the schema in the database:
$ psql reviewboard
psql (9.1.1)
Type help for help.
reviewboard=# \d diffviewer_diffset
Table public.diffviewer_diffset
Column | Type |
Modifiers
For what it's worth, I'm upgrading from 1.5.1 to 1.6.3 right now and I just
encountered the same error. I'm on Ubuntu 11.10, PostgreSQL 9.1, Python 2.7.
$ rb-site upgrade review-www
Rebuilding directory structure
Upgrading site settings_local.py
Updating database. This may take a while.
After some wrangling, I'm still stranded and not quite sure how to get past
this. Appreciate any help.
On Friday, September 16, 2011 11:48:13 AM UTC-7, Christian Hammond wrote:
Thanks for the info Joe. Glad 16.0 to 1.6.1 was more smooth. I'm not sure
what caused the problems with the upgrade
I did eventually make it past this issue by physically making the
modifications to the postgres database by hand. The evolution then
completed and I was able to 'revert' any changes I had done and
everything worked.
After this was all said and done - upgrading from 1.6.0 to 1.6.1,
'Just worked'
Thanks for the info Joe. Glad 16.0 to 1.6.1 was more smooth. I'm not sure
what caused the problems with the upgrade to 1.6.0 (those haven't been
showing up in our regression tests), but we'll continue to look into it.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -
Was upgrading from base 1.5 release to 1.6 with a postgres DB. I did
eventually get the evolutions to work by renaming existing columns and
dropping at least one empty table. This allowed the evolutions to complete
and I was able to get the site back up and running.
Joe
On Sat, Sep 10, 2011 at
Which 1.5?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Sun, Sep 11, 2011 at 1:02 PM, Joe Campbell
joseph.r.campb...@gmail.comwrote:
Was upgrading from base 1.5 release to 1.6 with a postgres DB. I
Hi Joe,
Sorry, this got lost in a flood of e-mails.
What version were you upgrading from?
What type of database?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Sep 8, 2011 at 1:05 PM, Joe Campbell
Running rb-site upgrade /var/www/cim-review after an easy_install -U
ReviewBoard resulted in this:
Rebuilding directory structure
Updating database. This may take a while.
/usr/lib/python2.6/site-packages/Django-1.3-py2.6.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE
11 matches
Mail list logo
