I had the same issue when I moved to a different server and
transferred the mysql db.
Drop table and sync/evolve worked for me. But ymmv.
Nithin.
On Jan 9, 6:04 am, "Christian Hammond" wrote:
> It sounds like something was hand-modified in the database enough to break
> things then. Basically,
It sounds like something was hand-modified in the database enough to break
things then. Basically, Django-Evolution keeps track of all changes to the
structure of the database, and something surprised it.
Is there any data in that table in your database?
The only things I can think of are:
1) Dr
Previously I was at revision #1556 (2008-10-27)
I have never downgraded.
I do have this table already as the error message states. Is there
anyway to move on past this error?
On Jan 8, 4:56 pm, "Christian Hammond" wrote:
> How old was your previous install? That table was added to the database
How old was your previous install? That table was added to the database many
months ago, and I haven't heard of it causing any problems. Did you at any
point upgrade, then downgrade to an older version?
Christian
--
Christian Hammond - chip...@chipx86.com
VMware, Inc.
On Thu, Jan 8, 2009 at 4:
Hi,
I'm trying to upgrade to the latest and greatest reviewboard svn code
base as I routinely do but, when I run the database evolution I get
the following error:
Error applying evolution: (1050, "Table
'reviews_reviewrequest_changedescs' already exists")
Full error below...
[reviewboard]$ sud