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. Postgres has a problem doing this in one
transaction, and the result is the error you're seeing.
I'm trying to find a way to make this work without regressing
elsewhere. I do have a tentative fix to Django-Evolution, so if I can
be reasonably sure it's safe, I'll perform a couple new releases.
On Monday, May 9, 2011, meadowman <keir.robin...@gmail.com> wrote:
> 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 an SQLite3 database as a bridge;
> something like a django-admin dump to json from the postgres installcreate a
> new beta1 site using sqlite3 and use django-admin to load the json to it.
> Then I could upgrade to beta2 - and evolve the sqlite3 site; create a new
> postgres install (using beta2) and load json into it from the upgraded
> sqlite3 site.
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at