Excellent :) Glad it works!
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, May 10, 2011 at 2:42 AM, meadowman wrote:
> Thank you Christian,
>
> I've just upgraded with the beta2.1 from beta1; smooth
Thank you Christian,
I've just upgraded with the beta2.1 from beta1; smooth as silk :-)
Regards.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--
A beta 1 to 3 upgrade should be fine. I won't release until it is.
Just to provide some detail on the problem. We use Django-Evolution
for database migrations. In beta 2, we added a new non-NULL boolean
field to a table, which Django-Evolution adds through an ALTER TABLE
followed by an UPDATE. Pos
Thank you for taking a look at the problem. It is very helpful to know that
it is not just a mistake on my part.
Is it likely that a beta1 -> beta3 upgrade will work? That is to say, might
the beta3 schema be such that the postgres issue is circumvented?
Alternatively, might I be able to use
Or not.
This is an annoying complication involving PostgreSQL's way of handling
certain types of alterations within a single transaction, and there's no
clear way of making this work without 1) major changes to django-evolution,
the project that handles database migrations, or 2) changing the data
I'll be putting out a hotfix within the hour that I hope fixes this for you.
Christian
On Monday, May 9, 2011, meadowman wrote:
> Hi, I tried upgrading to the beta2 build just now, without success.
>
> # rb-site --debug upgrade /var/www/reviews
> Rebuilding directory structure
> Updating databa
